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
When you click a button that contains bad code (including prims that don't yet compile), they don't indicate that they're invalid, and they throw an error on use. Instead, they should be unclickable, and they should show specifically that the code is invalid (like how the text gets red in JVM NetLogo).
The text was updated successfully, but these errors were encountered:
Agreed. I wasn't clear about this when I originally wrote the ticket, but any widget with invalid code (slider, plot, button, monitor, chooser) should be shown as broken.
If a plot has a runtime error it is squelched in the runWithErrorHandling() method from set-up-widgets.coffee to avoid interrupting the model. It should be displayed to the user in some non-intrusive way as it would be in NetLogo desktop. This is slightly different than the compile time error display, but I think it makes sense to address both at the same time.
When you click a button that contains bad code (including prims that don't yet compile), they don't indicate that they're invalid, and they throw an error on use. Instead, they should be unclickable, and they should show specifically that the code is invalid (like how the text gets red in JVM NetLogo).
The text was updated successfully, but these errors were encountered: