Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 11625

Summary:	java browser: try to restore selection
Product:	[Eclipse Project] JDT	Reporter:	Xavier Méhaut <xmehaut>
Component:	UI	Assignee:	JDT-UI-Inbox <jdt-ui-inbox>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	P5	Keywords:	helpwanted
Version:	2.0
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Xavier Méhaut

2002-03-19 05:14:46 EST

Hello,
It could be good to have the following feature ; when you change your class 
selection, it could be useful to be settled on the same selection as in the 
previous class. For instance, if in the class Toto I've selected toString(), I 
would like to be positionned onto the toString() method when I select the Titi 
class by default
Regards
Xavier

Comment 1 Erich Gamma

2002-03-19 05:47:51 EST

Dani, VA/Java had this sticky method selection feature. It can also be 
annoying...

Comment 2 Dani Megert

2002-03-19 06:37:00 EST

Not all users would like this so it would have to be a preference.
Would you only need it for the Java Browsing perspective or is this a general
request to be applied to other views e.g. the Packages view in the Java perspective?

Comment 3 Xavier Méhaut

2002-03-19 06:43:51 EST

I think it is useful more especially in the java browser perspective, but if it 
can be extended in others perspectives why not;-)
regards
Xavier

Comment 4 Dani Megert

2002-03-26 10:10:00 EST

changed summary

Comment 5 Erich Gamma

2002-05-12 09:03:26 EDT

defer to after 2.0

Comment 6 Dani Megert

2002-07-24 06:39:04 EDT

Post 2.0 review:

VAJ is quite stupid when doing this, e.g. if you select write(int) in class A
and then select B it selects the *first* method which is named "write". This
might be write(int) but might also be write(byte) - even though there might be a
method write(int) in class B.

Would configurable via Members view menu.

Comment 7 Dani Megert

2002-07-24 08:00:18 EDT

Candidate for 2.1

Comment 8 Dani Megert

2002-08-14 06:00:19 EDT

There are several problems with this feature
1) Eclipse keeps the state of editors i.e. when switching from A.java to B.java
and back you don't lose the context while in VA/Java there was always only one
editor pane.
2) VA/Java was in a closed world and could hard-wire the different panes (e.g.
Type, Member and editor pane). This is not the Eclipse philosophy: each view
should  be reusable in another perspective.
3) While setting the selection in the Members view could be achieved it would be
hard to force the editor to show the selected element without hard-wiring (see
also 2).
4) Losing the previous cursor position in editor B.java when switching (back)
from editor A.java to B.java is normally not what I (and probably you) want.
However this would happen because in A you might work on method m() and when
switching to B it would also switch to m() if there is such a member. This also
means that sometimes the editor keeps the position when switching and sometimes
it doesn't.

Not on the 2.1 nor 3.0 plan. Setting to WONTFIX. Please reopen if you think this
is a must have.

Comment 9 Xavier Méhaut

2002-08-14 06:06:29 EDT

I think that the need is still present. Maybe it is quite difficult to ensure 
with the way Eclipse is done today, but actually the requirement is still 
existing.
regards
Xavier

Comment 10 Dani Megert

2002-08-14 06:16:26 EDT

ok. fair enough.
I added the "helpwanted" keyword.

Moving to LATER since it's not on the plan.

Comment 11 Eclipse Webmaster

2009-08-30 02:36:51 EDT

As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.