Bug 4685

Summary:	Variables View re-positions on each step (1GETE8F)
Product:	[Eclipse Project] Platform	Reporter:	Darin Wright <darin.eclipse>
Component:	SWT	Assignee:	Grant Gayed <grant_gayed>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P4
Version:	2.0
Target Milestone:	2.1 M1
Hardware:	All
OS:	Linux-Motif
Whiteboard:

Description Darin Wright

2001-10-11 14:21:16 EDT

DW (6/4/2001 4:08:07 PM)
	118 - Linux

	If I expand the variables view tree such that the scroll bar is visible,
	on each step, the variables view updates but re-positions to the
	top of the tree.

DW (6/4/2001 4:23:58 PM) 
	It appears the variables view is switching to reveal the selected item
	which is the root of the tree by default.

DW (6/5/01 6:56:53 PM)
	Not critical. Note that on NT, the tree does not reveal the selection.
	Moving to ITPUI. Inconsistent viewer behavior between platforms.

KH (6/6/2001 4:11:14 PM)
	Moving to SWT for comment. 

	McQ (26/06/2001 9:23:47 AM) -
		Are the calling showItem with null? Does this behave differently on
		Windows than on Linux.

Comment 1 Darin Wright

2001-10-11 15:00:42 EDT

Please investigate if this problem still exists.

Comment 2 Darin Wright

2001-10-15 12:51:37 EDT

Assigning back to SWT - incorrectly reassigned to Jared B.

Comment 3 Mike Wilson

2002-05-24 18:48:53 EDT

Please check if this has been fixed and mark PR as either FIXED or 
LATER as appropriate.

Comment 4 Grant Gayed

2002-05-27 09:31:51 EDT

Still occurs in some circumstances.  Deferring...

Comment 5 Grant Gayed

2002-08-15 17:07:34 EDT

Reopening...

Comment 6 Grant Gayed

2002-08-15 17:14:43 EDT

The scrolling behaviour that results from invoking the different flavours of 
setSelection(*) are now consistent between Tree, Table and List.  This has been 
verified on win32 and motif, and gtk and photon will be taken care of soon.

Darin, note that the correct widget behaviour is to scroll whenever a 
setSelection method is invoked, so the Motif behaviour was actually the correct 
one.  Therefore the behaviour that you originally described as happening on 
Motif will now happen on win32 as well, so you'll have to change the debugger's 
implementation accordingly.