Community
Participate
Working Groups
How to see it - Close all editors - Load org.eclipse.osgi in the workspace - Open the "Package Explorer" view. Make sure all projects are collapsed. - In the "package explorer", make sure the "link with editor" is selected - Ctrl+Shift+T, open the type "DefaultClassLoader" - Select the class and open it. You will notice that the tree is first expanded then the editor is opened (or at least its the impression I got). Note that it only do it the first time you are going to the type, to reproduce you have to change type. If the "link with editor" option is off, there is no problem.
Without delving too deep into the PackageExplorer, here's my guess as to what's happening based on an examination of the workbench code... From the dialog you tell the file to open. Workbench page is told to open the file. The editor part is created. The part open event is fired. The package explorer reacts to the event, selecting the file in the package explorer. The page then activates the editor and brings it to the front of the stack. We can't go changing event orderings now, but the JDT guys might want to select the active file in a background UI job or something... Tod, can you please punt this somewhere based on your thoughts?
Unfortunately, Navigator and PackageExplorer do not share an implementation of Link To Editor.
I have a patch to PackageExplorerPart that will fix this. A similar patch should be applied to the Navigator and any other view that has Link To Editor functionality. Passing to JDT to consider. Will open a new bug for the Navigator case.
Created attachment 20198 [details] Patch against PackageExplorerPart
Incidentally, this is quite noticable in the Java Browsing perspective... every view can be linked to editor.
The job should check that the view's Tree has not been disposed in the interim.
I have a couple of concerns here: - executing this in a Job might cause some flashing since the revealing will not take place inside of the natice event loop. - adding all these jobs to the views some strange as well. Why don't we add a postPartActive event as we have a postSelectionEvent. This would fit better into the current stroy we have then adding jobs in all views. Nick, can you please comment.
Since this affects the Navigator too, let's move the discussion to bug 92274. Please see my latest comments there.
No further action planned. For details look at bug 92274.
setting to remind until status of bug 92274 changes
As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you.
