demon llama
New member
Whenever I happen to trigger an exception the UI lock mechanism enters an unknown state and until KoL is restarted (not even logged out/in) it will forever be screwy.
To reproduce (as of 9153):
- Trigger a NullPointerException in the GCLI (like my previous bug report -> 'maximize herp').
- Notice that we are in a 'grey' state and UI elements such as the Gear Changer Page are unusable (all dropdown boxes are locked).
- Note you can get the UI back to a 'green' state by navigating to a new location in the relay browser.
- As as you do another GCLI action (exception or not) it will go back to a 'grey' state and some UI elements will be locked.
I realize that the main culprit was the NullPointerException to begin with but perhaps there could be a better way the UI locks/unlocks so if something is interrupted you aren't left in these unknown states.
To reproduce (as of 9153):
- Trigger a NullPointerException in the GCLI (like my previous bug report -> 'maximize herp').
- Notice that we are in a 'grey' state and UI elements such as the Gear Changer Page are unusable (all dropdown boxes are locked).
- Note you can get the UI back to a 'green' state by navigating to a new location in the relay browser.
- As as you do another GCLI action (exception or not) it will go back to a 'grey' state and some UI elements will be locked.
I realize that the main culprit was the NullPointerException to begin with but perhaps there could be a better way the UI locks/unlocks so if something is interrupted you aren't left in these unknown states.
