Morpho

We need to be sure this is working reliably for the next release (1.2). Please
test thoroughly.

10/2/02 - higgins

According to the Java tutorial,

Rule: Once a Swing component has been realized, all code that might affect or
depend on the state of that component should be executed in the
event-dispatching thread

Currently, the SwingWorker class is used in a number of locations. namely

C:\work\morpho\src\edu\ucsb\nceas\morpho\editor\DocFrame.java
fixed

C:\work\morpho\src\edu\ucsb\nceas\morpho\Morpho.java
OK

C:\work\morpho\src\edu\ucsb\nceas\morpho\query\DeleteCommand.java
morphoFrame.setBusy(true);refreshDataPackageFrame violates rule

C:\work\morpho\src\edu\ucsb\nceas\morpho\query\ExportCommand.java
morphoFrame.setBusy(true); violates rule

C:\work\morpho\src\edu\ucsb\nceas\morpho\query\LocalToNetworkCommand.java
frame.setBusy(true); violates rule

C:\work\morpho\src\edu\ucsb\nceas\morpho\query\NetworkToLocalCommand.java
frame.setBusy(true); violates rule

C:\work\morpho\src\edu\ucsb\nceas\morpho\query\OpenDialogBoxCommand.java
morphoFrame.setBusy(true); violates rule

C:\work\morpho\src\edu\ucsb\nceas\morpho\query\OpenPackageCommand.java
morphoFrame.setBusy(true); violates rule

C:\work\morpho\src\edu\ucsb\nceas\morpho\query\OpenPreviousVersionCommand.java
morphoFrame.setBusy(true); violates rule

C:\work\morpho\src\edu\ucsb\nceas\morpho\query\RefreshCommand.java
morphoFrame.setBusy(true); violates rule

C:\work\morpho\src\edu\ucsb\nceas\morpho\query\ReviseSearchCommand.java
morphoFrame.setBusy(true); violates rule

C:\work\morpho\src\edu\ucsb\nceas\morpho\query\SearchCommand.java
morphoFrame.setBusy(true); violates rule

A recurring violation of the rule appears in several places where the 'flapping
butterfly' is set with a 'setBusy' command outside the event thead. (This uses
the "ProgressIndicator" class to reset the icon used in a JComponent). No code
bugs are obviously caused by this in Morpho, but we should probably make the
setBusy operation into a thread and use 'invokeLater' to execute in the eventThread.

fixed 'morphoFrame.setBusy(true)' so that the actual changing of the busy icon
is always done inside the event thread. This was done by changing the
ProgressIndicator class to implement Runnable and using involkLater in the
morphoFrame.setBusy method.

This fixes a problem in almost all the SwingWorker instances, but each still
needs to be examined for other component changes outside the event thread.

All the SwingWorker instances have been examined to look for Swing component
changed outside the event thread and any such changes have been moved to the
inside of the event loop.

(Since there were no apparently problems even in code that did change Swing
components outside the event loop, it is impossible to be sure that all
instances have been fixed!)

Original Bugzilla ID was 499