Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 360530 - GridVisibleRangeSupport should delay events
Summary: GridVisibleRangeSupport should delay events
Status: CLOSED INVALID
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Nebula (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Thomas Schindl CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-11 06:50 EDT by Peer Törngren CLA
Modified: 2021-07-05 11:40 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peer Törngren CLA 2011-10-11 06:50:54 EDT
Build Identifier: I20110613-1736

GridVisibleRangeSupport solve many performance problems in the grid, but if the label providers are slow or the columns are many (or both), scrolling gets badly distorted since the visible range is frequently updated. A workaround is to use a delayed observable that postpones the update until scrolling stops.

One workaround is to store the RangeChangedEvent in an observable property, and listen to this property using Observables.observeDelayedValue(….). This works quite nicely, but it introduces an intermediate step that also must manage additions and removals (accumulate and/or recalculate) since the delayed event only holds the most recent additions/removals.

Suggestion: It would be very nice if the GridVisibleRangeSupport would offer a way to specify a delay, and only fire events if the delay times out (in the spirit of other delayed observables in jface databinding).

Reproducible: Always

Steps to Reproduce:
See discussion in https://bugs.eclipse.org/bugs/show_bug.cgi?id=222402
Comment 1 Wim Jongman CLA 2019-12-12 15:56:52 EST
This bug does not have a target milestone assigned and is automatically closed as part of the 2.3.0 release cleanup.

It could be that this bug is accidentally closed for which we apologize.

If this bug is still relevant, please re-open and set a target milestone.