Bug 309455

Summary: [Viewers][DeferredContentProvider] Bottom rows without labels/icons
Product: [Eclipse Project] Platform Reporter: Mario Winterer <mario.winterer>
Component: UIAssignee: Platform UI Triaged <platform-ui-triaged>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3    
Version: 3.5   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: stalebug
Bug Depends on:    
Bug Blocks: 509006    
Attachments:
Description Flags
Example that shows the described behaviour
none
Suggested patch mario.winterer: review?

Description Mario Winterer CLA 2010-04-16 07:50:34 EDT 
Build Identifier: 20100218-1602, HEAD

When a DeferredContentProvider is used on a VIRTUAL table (viewer), the last n rows of the (visible) client area are blank, i.e. without labels/icons (where n is 1 or more, depending on the height of the table control, but usually less than 10).

When the keyboard is used to scroll down row by row, the last n rows stay blank, while the previously blank rows appear when they move upwards.

Reproducible: Always

Steps to Reproduce:
See code snippet attachment.
Comment 1 Mario Winterer CLA 2010-04-16 07:52:19 EDT 
Created attachment 165081 [details]
Example that shows the described behaviour
Comment 2 Mario Winterer CLA 2010-04-16 07:57:12 EDT 
This bug might be covered by bug #117165, which was reported in 2005 but is still not fixed.

I think this bug is caused by wrong calculation of the start and/or end index of the visible rows (i.e. the rows that are shown within the client area) in ConcurrentTableUpdator.

My attempt to fix this bug works so far; attachment #30273 [details] of bug #117165 seems to fix it too because they do the same index calculations there.
Comment 3 Mario Winterer CLA 2010-04-16 08:17:04 EDT 
Created attachment 165087 [details]
Suggested patch

Patch that fixed the wrong index calculation in ConcurrentTableUpdator and DeferredContentProvider.
Comment 4 Eclipse Genie CLA 2020-02-05 16:36:24 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.

--
The automated Eclipse Genie.