| java.lang.Object
 org.cougaar.mlm.debug.ui.UIBarGraphDisplay
| Method Summary | |
| public void | actionPerformed(ActionEvent e)
Redisplay bar graph.
This gets called:
if the dataSource (a collection) is notified that it was changed or
the user requests an update,
i.e. | | public void | run()
Create the data source for the bar graph, the bar graph, and its window. | | public synchronized void | subscriptionChanged(IncrementalSubscription container)
|
| UIBarGraphDisplay | | public UIBarGraphDisplay(UIPlugin uiPlugin, String planName, MessageAddress clusterId, String command)(Code) | | Display the specified data (either assets or scheduled assets)
in a bar graph.
All the work is done in the run method so
that the main user interface thread which creates this,
isn't waiting to fetch the information needed for the bar graph.
Parameters:
uiPlugin - this user interface plugin
Parameters:
planName - the name of the plan for which to display information
Parameters:
clusterId - the cluster for which to display information
Parameters:
command - UIDisplay.ASSET_SCHEDULE_COMMAND or UIDisplay.ASSETS_COMMAND |
| actionPerformed | | public void actionPerformed(ActionEvent e)(Code) | | Redisplay bar graph.
This gets called:
if the dataSource (a collection) is notified that it was changed or
the user requests an update,
i.e. this is used for changes stimulated either internally
(the data changed) or externally (the user wants an update).
The reason for the duality is that we can listen for changes in the
LOCAL cluster, but not in REMOTE clusters.
If the change was stimulated internally, then the data source got
the change, and updated its values, and this simply redisplays;
if the change was stimulated externally (by the user), then this
first calls the data source to update the values, and then redisplays.
Parameters:
e - the action event (object added, deleted or changed) |
| run | | public void run()(Code) | | Create the data source for the bar graph, the bar graph, and its window.
Fill in the graph here so that delays in accessing information
from clusters don't affect the main user interface thread.
Register as a listener for changes in the information in the bar graph.
|
|
|