Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 327597 - Scrolling issues with TableViewer
Summary: Scrolling issues with TableViewer
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.3.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-12 14:32 EDT by Sujeet Mishra CLA
Modified: 2019-11-08 04:37 EST (History)
6 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sujeet Mishra CLA 2010-10-12 14:32:08 EDT
Build Identifier: M20071023-1652

A video of the problem can be found at the link below 

Table viewer does not scroll to the last record in the table 
On careful observation we find that though there are more entries under the perceived last entry in the table , the table viewer's scroll bar shows as if its the end of the table .

A video of this scenario can be sent on request 

Reproducible: Always

Steps to Reproduce:
1.Modify the window size  of an eclipse RCP application having a table viewer 
such that the number of elements in the table is around 2X the vertical size 
2.On scrolling down the table although the scroll bar appears at the end position , there are few entries still not revealed 
3.Place mouse pointer on scroll bar 
4.Scroll bar moves down to reveal the other entries
Comment 1 Felipe Heidrich CLA 2010-10-12 16:06:18 EDT
We need code that we can run here to debug the problem.
Can you reduce the problem to a simple eclipse plugin or swt snippet ?
a snippet would be better: http://www.eclipse.org/swt/snippets/ (see second paragraph).
Comment 2 Lars Vogel CLA 2019-11-08 04:37:32 EST
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.

If the bug is still relevant please remove the stalebug whiteboard tag.