Bug #4185
closedTabManager acting strangely
0%
Description
The TabManager is calling intializeTabs() twice. Once at startup and once at shutdown. Each time, the parent arg is different. The first time the parent is 'frame1', the second time it is 'frame3'. Need to figure out why TabManager is getting called on shutdown at all.
Updated by Chad Berkley over 15 years ago
This seems to only happen for WRP. Maybe because there are way more tabs and frames in the WRP interface. I'm seeing an exception when kepler shuts down that doesn't seem to make any sense. It is:
java.lang.Exception: Outline TabPane specified in config.xml was not found in the TabManager.
[run] Make sure you have specified the TabPane in configuration.xml
[run] at org.kepler.gui.ViewManager.addConfiguredTabPanes(ViewManager.java:346)
[run] at org.kepler.gui.ViewManager.initializeViews(ViewManager.java:83)....
I checked the configuration and it looks like both the config.xml and configuration.xml files are set correctly for the "Outline" tab that it is complaining about. I'm digging in to figure out why this is getting called twice in the first place.
Updated by Chad Berkley over 15 years ago
WorkflowRunManagerPanel was falsely assuming that calling topLevel() on a model would return a CompositeActor. Instead, if there was no model loaded, topLevel() returns the configuration. There was a classcastexception being thrown when this happened which for some reason, caused the tabs to reinitialize. I fixed the cast now it seems to work fine.