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
The GUI becomes unresponsive during the build phase of a model run. After diagnosing a bit, it looks like the Event Dispatcher Thread (EDT) is occupied after the build button is pressed. This seems to be a basic Swing design problem. I have fooled about with SwingWorkers to try to fix this issue, but without success. This isn't too surprising as I have no previous experience with Java Gui design. Nevertheless, the issue would be useful to fix, as the code currently does not provide any user feedback even where the build phase is lengthy (the Output stream window should ideally provide some feedback via System.out statements).
The text was updated successfully, but these errors were encountered:
The GUI becomes unresponsive during the build phase of a model run. After diagnosing a bit, it looks like the Event Dispatcher Thread (EDT) is occupied after the build button is pressed. This seems to be a basic Swing design problem. I have fooled about with SwingWorkers to try to fix this issue, but without success. This isn't too surprising as I have no previous experience with Java Gui design. Nevertheless, the issue would be useful to fix, as the code currently does not provide any user feedback even where the build phase is lengthy (the Output stream window should ideally provide some feedback via System.out statements).
The text was updated successfully, but these errors were encountered: