[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Newsgroup Home]
[news.eclipse.platform.rcp] Re: is there a preferred RCP mechanism for updating editors based on model-changes caused in a view?

Question is not related to RCP. When the model changes you don't get ResourceChangeEvents. You get those when the resource changes. That is, when the file is renamed or moved, but not when its altered while open.

You need to register a listener to your model. Your model needs to fire events when it makes significant changes. Typically the edit part registers to listen to the model withn its 'activated' and deregisters when its 'deactivated' I believe.


CL


Paul Keyser wrote:
R3.1.1

Classic situation:
a palette-like View, which causes changes to the data-model shown in the Editor (e.g., through a popup-menu item in the View) => how to ensure that the editor updates its display of the model?


Eclipse-PDE solution: resource-changes and a ResourceChangeListener; works fine

Problem: in RCP, no such thing as Resources ... (also, my editor is not a text-editor)

So: is there a preferred alternate in RCP to ResourceChangedListeners? or do I just roll my own set of model-listeners, etc.? (I'm fine with doing either, but I don't want to reinvent the wheel and find myself fighting Eclipse; I'd rather work with it!)

thanks,
Paul

Note: these sources did not address the issue:

1) Help in the 3.1 Eclipse (http://127.0.0.1:51279/help/topic/org.eclipse.platform.doc.isv/guide/rcp_actions.htm)


2) This newsgroup, although two threads were tantalizing: "Linking View vs Editor(ISelectionProvider ISelectionListener)" (but my situation does not involve selection), and "How does a view listen to a editor's action" (which is the inverse of my problem, but the recommended solution depends on making use of the OutlineView, which seems as far as I can see to contain only SelectionChangedListener stuff)


3) 3.0-FAQ's, chapters 13-14

4) JDG2E Help

5) RCP Tutorial

6) Text Editor RCP example (has no View, so ...)

7) Browser example (is not editable, so ...)