-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Buttons should use "ownsPrimaryJobs" JobOwners #145
Comments
Thanks for the report, @qiemem! (And for the other ones as well!) Do you have any examples of "unexpected and bizarre behavior" that I could try to reproduce to test the fix? |
The case in which it arose is fairly complex, though it was consistent, and it no longer occurred after the above change. Naturally, when I try to create a small example for testing, I can't get the problem to occur (I did indeed revert to an unmodified xw)... I'll keep trying to come up with a case. Sorry :( I know how frustrating it is to have bug report without a simple reproducible case. |
You've found a subtle bug in fairly untested code and proposed a fix that makes sense and seems to have solved the problem in the context you found it. I can't really ask for more! If you can come up with a test case, that will be awesome, but if not, don't sweat it; I'll just merge as is. Thanks again! |
mark xw button's JobOwner as primary (fix #145)
Currently, xw buttons can have their jobs run concurrently with NetLogo buttons. This can give rise to some very unexpected and bizarre behavior. I believe their
JobOwner
s should be initialized with:The text was updated successfully, but these errors were encountered: