Community
Participate
Working Groups
GMF allows to create Diagram Editor and we'd like to synchronize selection in this editor with the selection in "Project Explorer" view if "Link Open editors with content in navigator" button is pressed. GMF provides content of the diagram below the diagram file node in "Project Explorer", specific GMFLinkHelper class was created and registered. The probelm is: selection returned from GMFLinkHelper.findSelection(IEditorInput input) will be merged with one returned by ResourceLinkHelper.findSelection(IEditorInput input). As a result diagram file node will be selected in Project Explorer in any case. We’d like to get rid of this selection – we only have to select some sub-node(s) of diagram file returned by GMFLinkHelper. There should be a way to unregister ResourceLinkHelper for some particular cases. Looks like for now we can only work with custom IEditorInput implementations (not instanceof IFileEditorInput).
Looks like this question is a little bit more generic – it is assumed that ILinkHelper will not change returned selection while working with Editor. So, Project Explorer provides the possibility to select a node in tree in accordance with Editor, but does not allow to change this selection while editing (changing selection in editor). In other words, selection in Project Explorer will be the same while working with the same editor with "Link Open editors with content in navigator" switched on. In case of opposite synchronization it is possible to move selection in editor in accordance with selection in Project Explorer (e.g. select java method/attribute in Project Explorer -> corresponding line will be selected in editor). So, the question is more generic: Should we allow to propagate selection of file structure parts into the Project Explorer by ILinkHelper or file-based selection is enough?
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
