Community
Participate
Working Groups
Call Hierarchy defined as a tabbed view Package Explorer is defined as a Fast View Start on Class A (any class) Go to a method and Right Click on Open Call Hierarchy Click on a class other than the current one (Class B) Note: Class B is now active in the editor Open the Package Expolorer Package Explorer has Class A still highlighted (instead of Class B) Click on the editor (which still has Class B) Open the Package Expolorer Package Explorer has Class B is now correctly highlighted Click on the editor
Was able to reproduce this even with the resource navigator, so I believe this is a problem with part activation events.
We can discuss tomorrow, but I don't believe it's an event problem. If you have both classes open and you are using the Call Hierarchy view to switch between them you are changing the editor but not activating it. As soon as you activate the editor, it links to the correct file. The package explorer doesn't have to be a fast view to show this behaviour. This might be fixable by having the navigator and the package explorer listen for partBroughtToTop() as well as partActivated(). Is this behaviour consistent with 3.1.2? PW
Is this still a problem in 3.3? PW
Changes requested on bug 193523
Created attachment 78908 [details] Patch to provide the requested behaviour for the Navigator. Reproduced on I20070920-0936. Should a separate bug be filed for JDT?
Created attachment 95134 [details] Updated patch against HEAD. This is still a problem on I20080401-0851.
Released to HEAD >20080408 PW
This is only partically fixed in the Resource Navigator, see bug 226288 PW
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.