|Re: Editor behavior [message #1073111 is a reply to message #1072426]
||Wed, 24 July 2013 06:58
| Cedric Moonen
Registered: August 2009
Thanks for the reply.|
There is no need to use MInputPart in order to have an 'editor'; in fact the 3.x compatibility layer doesn't use it. All Parts inherit MDirtyable, meaning that they can be
marked as dirty and already participate in the prompts on shutdown...
Ok, what is the purpose of the MInputPart then ? I thought it is to be used for parts that should receive input (like an editor-like behavior), and that's also what is described in this tutorial: http://www.vogella.com/articles/Eclipse4Editor/article.html
If you need to store information about the 'file' being edited...consider using the part's 'persistedState' map.
Sorry, I don't really understand this. Isn't the persistedState used to persist the current state of the part, so that when it is re-opened later, it would be displayed in the same state as it was left ?
What I want to achieve is passing my own object to the part, so that it is available in the @PostInitialize method. I could of course create my own set method and create the contents of my part in there, after the input has been set, but I don't really like that idea...
Powered by FUDForum
. Page generated in 0.29338 seconds