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

Bug 360530

Summary:	GridVisibleRangeSupport should delay events
Product:	z_Archived	Reporter:	Peer Törngren <mbr-eclipse>
Component:	Nebula	Assignee:	Thomas Schindl <tom.schindl>
Status:	CLOSED INVALID	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	cgross
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description Peer Törngren

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

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.