Paul, thank you I understand the problem with the instantation now! Although a work-around for the whole situation can be based upon @CanExecute where I may perform the synchronization. It seems in this case that @CanExecute is called just before the resp. elements are shown, while the argued @Initialize would have been called on instantiation of "Class URI".
I have opened bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=397249 for the issue. cheers, marco Am 30.12.2012 um 14:00 schrieb Paul Webster <[email protected]>: > We don't want to instantiate anything (and possibly start a number of > bundles) just to synchronize states. ToggleState from 3.x serves that > purpose, to save the state so that on restart it can be set correctly. > > In Eclipse4, the same pattern would be that the HandledContributionItem keeps > a persistedState key up to date in the model, and as part of a HCI creation > it reads that state. > > Although that begs the question, if the model item is "selected" are we just > not setting the checked state on startup. > > I'd also suggest you open a bug, these kinds of discussions should happen > there. > > Later, > Paul > > -- > Paul Webster > Hi floor. Make me a sammich! - GIR > _______________________________________________ > e4-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/e4-dev _______________________________________________ e4-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/e4-dev
