Semtools

Alternatively, create StateChangeEvents that reflect the change regardless of where it happens, so that updates to the annotation model can be reflected in both the tabular and the madlib views.

here's my thinking:
-there should be a [rather lightweight] class that holds the tabbed pane
-this AnnotationTabPane keeps track of which tab is currently active
-if the Column Annotation tab is active and a column selection change event
occurs, the current state of the Column Annotation is saved before anything
else happens.
-if the tab is not active, then nothing needs to be saved.
-if the tab was just active (and is being navigated away from) then the
annotation needs to be saved.

*I use "save" in the temporary sense, not in the "to disk" sense.

this is working now. I've restricted how you can use the AnnotationPage's methods so as to avoid duplicating mappings.
The AnnotationTabPane is now responsible for keeping track of the selected state of the tabs and saving when need be. More importantly it keeps the tabs in synch with the latest state of the annotation as it is modified through various parts of the UI.

and it's back

-added logging
-use member variable for annotation page reference (used in event handling methods)
-reset the annotation page values when the appropriate column/tab selection events occur (this was not always happening, hence the duplication bug)

i'm pretty sure this won't be reopened...

Original Bugzilla ID was 4836