Bug 298394 - ExpandBar scrolls to less
Summary: ExpandBar scrolls to less
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.5.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-22 07:06 EST by Holger Grote CLA
Modified: 2019-09-06 16:05 EDT (History)
1 user (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 Holger Grote CLA 2009-12-22 07:06:43 EST 
Build Identifier: 20090920-1017

If you create an ExpandBar with a lot of entries, the Scrollbar gets resized correct, but if you click on the Scrollbar to scroll or click on the arrows of the scrollbar the scrollbar scrolls only a bit.

The problem is that the variables 'increment' and 'pageIncrement' of the Scrollbar are not set. The reason for this is that the ExpandBar does an OS call in setScrollbar() instead of doing getVerticalBar().setValues(...) which sets the variables.

Reproducible: Always

Steps to Reproduce:
See the ExpandBar in the SWT-Examples application. The page scrolling also scolles not a whole page.
Comment 1 Felipe Heidrich CLA 2010-01-18 14:19:37 EST 
Can you post a simple test case ?

I'm not sure what you mean by 'SWT-Examples application', is that the Control Example ?
Comment 2 Holger Grote CLA 2010-01-19 04:26:38 EST 
Yes, it is the Control example (org.eclipse.swt.examples.controlexample.ExpandBarTab) which also demonstrates the problem.
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:05:24 EDT 
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.