Bug 279575 - [Navigator] Navigator: Link with Editor fails after startup
Summary: [Navigator] Navigator: Link with Editor fails after startup
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.5   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-09 04:36 EDT by LeO welsch CLA
Modified: 2019-09-06 16:11 EDT (History)
2 users (show)

See Also:


Attachments
Screenshots from the Eclipse (354.24 KB, application/octet-stream)
2009-06-09 11:30 EDT, LeO welsch CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description LeO welsch CLA 2009-06-09 04:36:56 EDT
Build ID: I20090528-2000

Steps To Reproduce:
A)
Open a file from a Java-project with Java-editor.
Navigator is on Fast View (don't know if this matters)
Link with Editor is selected.
File is displayed properly.

B)
Close Eclipse. Launch Eclipse.
Click into the Editor.
Open Navigator ==> Selection is not properly, cause the Link does not work.
Click once more into the Editor
Open Navigator ==> Selection works properly.

Seems like the init-procedure of the Navigator is done the wrong way. Step is reproducable with starting Step B.

Not a big issue, but an annoying one, cause any time I launch Eclipse and review with Navigator, the the link is misplaced. The Bug is there for the last couple of years and I thought, perhaps it solves by itself ;) Unfortunately not ==> I enter a Bug.

More information:
Comment 1 Boris Bokowski CLA 2009-06-09 10:43:50 EDT
> The Bug is there for the last
> couple of years and I thought, perhaps it solves by itself ;) Unfortunately not
> ==> I enter a Bug.

Thanks for finally doing that!

However, I could not reproduce the bug unfortunately. Which navigation view are you using? "Package Explorer", "Project Explorer", or "Navigator"?

Is there anything else that is special about your setup? For example, can this be reproduced using a new workspace, and if yes, what are the exact steps?(In reply to comment #0)
Comment 2 LeO welsch CLA 2009-06-09 11:30:27 EDT
Created attachment 138680 [details]
Screenshots from the Eclipse
Comment 3 LeO welsch CLA 2009-06-09 11:34:02 EDT
I have enclosed screenshots with a brief description-file.

As you could see from the attachment, I have troubles to retest it with a newly created project. Frankly said, I have no clue, why the filter does not work there. If I would have I would have retested it as well with a new project.
Comment 4 Krzysztof Daniel CLA 2009-06-09 11:41:33 EDT
This issue is very similar to bug 277120
Comment 5 LeO welsch CLA 2009-06-09 16:20:41 EDT
Seems so, but as you can see, on screenshot 64, the project is expanded.

My personal guess: At the startup something must be done additionally then when displaying it once more. So, the tree is initated. And I guess the selection is set prior to building of the tree is completed. 

And perhaps this is related to the mentioned bug, but no clue about the internals.

Additional question: Is screenshot 61 worth opening another ticket, or is it just a misconfiguration? (Or a misunderstanding that the projects should be displayed in Navigator the same way as in Project-Explorer). I would say, it's a bug, but if there is a simple explanation, then I would save me time to open another entry ;)
Comment 6 Susan McCourt CLA 2009-06-30 17:52:34 EDT
Reassigning to [Navigator] (although some of the screenshots address the package explorer).  
Comment 7 Eclipse Webmaster CLA 2019-09-06 16:11:07 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.