You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The minimal case to reproduce is a model with a chooser with options true and 1. Opening the chooser will cause it to repeatedly flash until clicking somewhere else in the model, and the value cannot be updated.
In Firefox the window opens just fine, but both of the values aren't select-able. Jason reports he doesn't see this problem in Opera or Chrome on Linux.
After tracing through the code, the offending line is this call to @ractive.update(). Removing that call removes the unwanted flashing behavior (or unable to select Firefox behavior). The strange thing is the choosers are not being updated in the related code above the call that I can see, so there really isn't anything for Ractive to update with the choosers.
This only affects models that mix 1/true or 0/false in chooser options, which should not be common. The workaround for models that do need both in a chooser would be using alternative strings for the values and converting them in NetLogo code when changed.
The text was updated successfully, but these errors were encountered:
The minimal case to reproduce is a model with a chooser with options
true
and1
. Opening the chooser will cause it to repeatedly flash until clicking somewhere else in the model, and the value cannot be updated.In Firefox the window opens just fine, but both of the values aren't select-able. Jason reports he doesn't see this problem in Opera or Chrome on Linux.
After tracing through the code, the offending line is this call to
@ractive.update()
. Removing that call removes the unwanted flashing behavior (or unable to select Firefox behavior). The strange thing is the choosers are not being updated in the related code above the call that I can see, so there really isn't anything for Ractive to update with the choosers.This only affects models that mix
1
/true
or0
/false
in chooser options, which should not be common. The workaround for models that do need both in a chooser would be using alternative strings for the values and converting them in NetLogo code when changed.The text was updated successfully, but these errors were encountered: