Bug 141102 - [WorkbenchParts] Link With Editor not pointing to current file being edited
Summary: [WorkbenchParts] Link With Editor not pointing to current file being edited
Status: REOPENED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: contributed
Depends on: 226288
Blocks: 226180 226181
  Show dependency tree
 
Reported: 2006-05-10 13:51 EDT by Cary Sweet CLA
Modified: 2019-09-06 16:07 EDT (History)
1 user (show)

See Also:


Attachments
Patch to provide the requested behaviour for the Navigator. (1.21 KB, patch)
2007-09-20 19:50 EDT, Remy Suen CLA
no flags Details | Diff
Updated patch against HEAD. (1.07 KB, patch)
2008-04-07 20:03 EDT, Remy Suen CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Cary Sweet CLA 2006-05-10 13:51:57 EDT
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
Comment 1 Boris Bokowski CLA 2006-05-10 17:19:55 EDT
Was able to reproduce this even with the resource navigator, so I believe this is a problem with part activation events.
Comment 2 Paul Webster CLA 2006-05-10 21:48:11 EDT
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
Comment 3 Paul Webster CLA 2006-09-28 15:17:51 EDT
Is this still a problem in 3.3?

PW
Comment 4 Denis Roy CLA 2007-06-22 09:33:27 EDT
Changes requested on bug 193523
Comment 5 Remy Suen CLA 2007-09-20 19:50:34 EDT
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?
Comment 6 Remy Suen CLA 2008-04-07 20:03:18 EDT
Created attachment 95134 [details]
Updated patch against HEAD.

This is still a problem on I20080401-0851.
Comment 7 Paul Webster CLA 2008-04-08 15:28:01 EDT
Released to HEAD >20080408
PW
Comment 8 Paul Webster CLA 2008-04-09 10:24:25 EDT
This is only partically fixed in the Resource Navigator, see bug 226288

PW
Comment 9 Eclipse Webmaster CLA 2019-09-06 16:07:38 EDT
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.