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
Progress bar and Plot button are busy when Spread parses the trees (AnalyzeTrees method), but are released before the plotting is done. Finished message is shown prematurely.
What should happen:
Progress bar and Plot button should be released only when plotting is done.
What is REALLY happening:
Apparently the Processing AnimationThread is not working from SwingWorker thread pool invoked by the doInBackground() method. Because of that the done() method is invoked when AnalyzeTrees() finishes it's job (as it is running in SwingWorker
thread pool). The relevant lines of code are in gui.TimeSlicerTab.java::ListenGenerateProcessing (794 : 980)
Possible solutions:
Somehow get the AnimationThread to run in the Swing Worker thread pool.
Run the job in EDT using invokeLater() (risking that application freezes)
Other
Other Comments:
Actually the same holds with other Processing templates. Yet there the plotting takes such a short time that the issue is not observable from the user point of view. This however becomes clear when the threads are observed in profiler.
The text was updated successfully, but these errors were encountered:
How to reproduce the bug:
What happens:
Progress bar and Plot button are busy when Spread parses the trees (AnalyzeTrees method), but are released before the plotting is done. Finished message is shown prematurely.
What should happen:
Progress bar and Plot button should be released only when plotting is done.
What is REALLY happening:
Apparently the Processing AnimationThread is not working from SwingWorker thread pool invoked by the doInBackground() method. Because of that the done() method is invoked when AnalyzeTrees() finishes it's job (as it is running in SwingWorker
thread pool). The relevant lines of code are in gui.TimeSlicerTab.java::ListenGenerateProcessing (794 : 980)
Possible solutions:
Other Comments:
Actually the same holds with other Processing templates. Yet there the plotting takes such a short time that the issue is not observable from the user point of view. This however becomes clear when the threads are observed in profiler.
The text was updated successfully, but these errors were encountered: