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

Bug 96782

Summary: [navigation] flashing of the editor when reselecting an element from the outline
Product: [Eclipse Project] Platform Reporter: Tom Hofmann <eclipse>
Component: TextAssignee: JDT-UI-Inbox <jdt-ui-inbox>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: P4    
Version: 3.1   
Target Milestone: 3.2   
Hardware: PC   
OS: Linux-GTK   
Whiteboard:
Attachments:
Description Flags
96782.png none

Description Tom Hofmann CLA 2005-05-26 10:00:26 EDT
N20050526

- folding off (can also be reproduce with folding on)
- open AbstractTextEditor
- open the outline view
- select AbstractTextEditor in the outline
- select the first field (TAG_CONTRIBUTION_TYPE) in the outline

- select AbstractTextEditor in the outline again

-> note that parts of the editor flash quickly.
Comment 1 Dani Megert CLA 2005-05-26 10:30:39 EDT
Investigate for RC2 (time permitting).
Comment 2 Dani Megert CLA 2005-05-28 06:38:28 EDT
Tom, please whether you can still reproduce using the patch I gave you.
Comment 3 Tom Hofmann CLA 2005-05-30 03:39:54 EDT
Created attachment 21945 [details]
96782.png

It does not flash any longer, but I see this behavior:

The text widget's scroll position is not correctly initialized when first
shown, i.e. when opening StyledText.setSelection(Point) from the package
explorer, the selected method is shown. However, the vertical scrollbar still
show the top-most position, the horizontal bar shows the left most position,
although neither is true (see screenshot).

Upon moving the caret such that it goes beyond the viewport boundaries, the
scrollbars are correctly set to the expected position.

Upon scrolling the editor using the mouse wheel, the opposite happens: the
editor is scrolled to the position that the scrollbars indicated (offset 0).
Comment 4 Dani Megert CLA 2005-06-08 04:28:22 EDT
Marking as duplicate of bug 93845: the changes for that bug will fix this one.

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