For example, open any, mess up the code (to induce a compile error), then delete a button in the interface. You will jump to the code tab even though the change you just made has nothing to do with the error. This is both annoying when trying to model changes that require significant UI and code changes as well as slightly deceptive in that it makes it seems like the widget deletion is related to the code error.
My proposed solution:
When the code tab is in error, it should remember the error. A tab jump should only occur as the result of a widget change if the compile error has changed.
@qiemem Not sure if this would solve your problem, but a related fix was added recently, see this PR: https://github.com/NetLogo/NetLogo/pull/2261. Let me know if that fixes the problem!
For example, open any, mess up the code (to induce a compile error), then delete a button in the interface. You will jump to the code tab even though the change you just made has nothing to do with the error. This is both annoying when trying to model changes that require significant UI and code changes as well as slightly deceptive in that it makes it seems like the widget deletion is related to the code error.
My proposed solution:
When the code tab is in error, it should remember the error. A tab jump should only occur as the result of a widget change if the compile error has changed.