Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 59449 - [Navigator] Too much scrolling in navigator when link to editor enabled.
Summary: [Navigator] Too much scrolling in navigator when link to editor enabled.
Status: RESOLVED DUPLICATE of bug 42175
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Nick Edgar CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-04-21 11:15 EDT by Mike Wilson CLA
Modified: 2004-04-23 13:00 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Wilson CLA 2004-04-21 11:15:03 EDT 
Not sure if there is anything that can be done about this, but it seems that the tree expansion/scrolling 
behavior causes a lot flash when clicking between editors. Could this be fixed? Possibly by detecting the 
bad cases and turning off refresh?
Comment 1 Nick Edgar CLA 2004-04-22 11:44:31 EDT 
The last time I looked at this, the viewer code was just populating and
expanding parent elements, and then setting the selection once at the end.
We don't turn refresh off, but it's something we could try.

As much as I'd like to, I don't have the cycles to look at this right now. 
Steve, would it be possible for you or someone else on the SWT team to help out
with this, e.g. look into whether the Workbench is using SWT appropriately here,
and make some recommendations?
Comment 2 Mike Wilson CLA 2004-04-23 09:13:48 EDT 
Note that you can't blindly turn of refresh in all cases, since this causes potentially worse flash. The 
trick is to detect whether the appearance of each specific expansion will be better or worse (i.e. one 
redraw at the end is better than three individual expansions where each one scrolls the widget (which is 
something I have seen)).
Comment 3 Steve Northover CLA 2004-04-23 10:36:53 EDT 
Yes, Grant and I will look at it.
Comment 4 Nick Edgar CLA 2004-04-23 13:00:40 EDT 
Reopened bug 42175, which is believed to be the cause of this.

*** This bug has been marked as a duplicate of 42175 ***