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
{{ message }}
This repository has been archived by the owner on Jan 26, 2019. It is now read-only.
Currently, when a user clicks on a button, the button gets disabled and is supposed to only be re-enabled once the asynchronous callback to IdleLands is completed.
But it happens a lot that when other asynchronous callbacks are completed, the GUI gets updated to reflect e.g. a new action, thus enabling the button before the intended callback is complete.
This should be fixed by keeping track of intended and non-intended callbacks trying to update the gui, through a derived class of Windows.Forms.Button
The text was updated successfully, but these errors were encountered:
Currently, when a user clicks on a button, the button gets disabled and is supposed to only be re-enabled once the asynchronous callback to IdleLands is completed.
But it happens a lot that when other asynchronous callbacks are completed, the GUI gets updated to reflect e.g. a new action, thus enabling the button before the intended callback is complete.
This should be fixed by keeping track of intended and non-intended callbacks trying to update the gui, through a derived class of Windows.Forms.Button
The text was updated successfully, but these errors were encountered: