I am using Nebula GridTreeViewer and Grid. I am also using GridVisibleRangeSupport to get to visible rows. The grid has 60 columns. I use visible rows to get additional data for the rows asynchronously and lazily update them. It works fine until when I expand a node and data coming back is about 1500 rows. After that it seems to slow down or freeze on any kind of mouseclick on the grid (closing/expanding the node, scrolling) or viewer refresh programmatically.
Even when I removed asynchronous processing, by mere attaching of the
GridVisibleRangeSupport slowed down everything when rows returned were about
1500.
If I don't attach GridVisibleRangeSupport then those 1500 rows do not seem to
slow down or freeze the UI.
My project requires to get additional data from database for visible rows(e.g.
when scrolling).
Nebula Grid I have is from year 2012 - ver = 1.0.0.201209220511
I will appreciate if somebody can give me some input.
Dhiresh
To participate in the discussion, go here:
https://www.eclipse.org/forums/index.php?t=rview&frm_id=64
_______________________________________________
nebula-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/nebula-dev
