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

Bug 333303

Summary: scrollbar page increment too big for tree-structured grids
Product: z_Archived Reporter: Markus Bohr <markus.bohr>
Component: NebulaAssignee: Thomas Schindl <tom.schindl>
Status: CLOSED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: cgross, laurent.caron
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description Markus Bohr CLA 2010-12-29 09:50:21 EST
Build Identifier: eclipse: 3.5.1  nebula: 1.1.2

A Nebula Grid Table widget bug which appears for widgets that have subitems / tree structure. 
getVisibleRange() then also contains the invisible items, causing the scrollbar to use a too big page increment, with the effect that grid items are skipped doing a page scroll down or up. 
Unfortunately I see no way to fix this in class "PuGrid", so we have to wait for a Nebula fix (no one discovered in newsgroups at the moment) 

Either the getVisibleRange() functionality is corrected, i.e. to call getRowRange() inside or to test against gridItem.isVisible(),
or the Grid() constructor is modified the below way which would however only be a workaround: 

old: 
                public void widgetSelected(SelectionEvent e) { 
                    GridVisibleRange visibleRange = getVisibleRange(); 
                    vScroll.setPageIncrement(visibleRange.items.length - 2); 
                } 

new: 
                public void widgetSelected(SelectionEvent e) { 
                    RowRange rowRange = getRowRange(getTopIndex(), getBottomIndex(), false, false); 
                    vScroll.setPageIncrement(rowRange.rows - 2); 
                }

Reproducible: Sometimes

Steps to Reproduce:
1. open a tree-structured grid table widget that contains much more items to display than able to display
2. be sure to have all subitems collapsed, so they are not visible
3. scroll down or up a page clicking on the scrollbar
Comment 1 Laurent CARON CLA 2019-09-30 11:27:09 EDT
Bug tried today, does not seem to exist anymore