If I am not updating the Grid, do I need to specify the 'versionProperty' ? I just set it to be the same as my total count ('results') thinking that should uniquely identify the 'version'. Could use (or incorrect use) of version property be what is maybe causing my 'constant update' problem?
Did you get an answer to this question about the versionProperty? I too have the same question and did not find an answer on this thread.
Did you get an answer to this question about the versionProperty? I too have the same question and did not find an answer on this thread.
The version's property use is totally up to you and right now no part of the livegrid's implementation listens to the "versionchange" event.
However, if you pass a version property, the store will read it out and fire this event if the value changes between two (buffer) requests.
What you do with it is up to you - if you have pending selections (i.e. ranges of row-indexes (NOT! record indexes)) which should be selected, but for which no records have been loaded yet, you could remove those selections as you would not know if any data has been slipped right in between this range of selections, which could lead to data inconsistency if you're about to send a "delete" request to the server with the ranges of pending selections available.
Anyway, the component has been refactored up to a degree where handling selections and pending selections has been greatly improved and simplified, along with other changes to the UI so the component looks like a "real" Ext grid. This changes will make it into the 0.2 branch before backwards compatibility will be broken (due to Ext 2.2 support).
Last edited by ThorstenSuckow; 31 Aug 2008 at 10:08 AM.
Reason: dude, whee's my coffee smiley?
Thank you for your fixes. Especially thanks for fixed the problems if there were less records than could be displayed.
Do you have any plans to implement a fix for the scrolling bug in the next version or is that a lower priority? For us it's the highest priority so we cannot use the actual version because of that bug. We're using Ext 2.2. You said a week before you would implement it into version 0.2. Am I right that you are working on it?
Thank you for your fixes. Especially thanks for fixed the problems if there were less records than could be displayed.
Do you have any plans to implement a fix for the scrolling bug in the next version or is that a lower priority? For us it's the highest priority so we cannot use the actual version because of that bug. We're using Ext 2.2. You said a week before you would implement it into version 0.2. Am I right that you are working on it?
Ah no... Ext 2.2 support will be in 0.3... this is scheduled for end of september, at last my bugtracker tells me so
Is it possible to have pagination in LiveGrid? If the total count is very large (greater than 10000), it will be hard to control the scroll bar to navigate to a particular record.
In normal GridPanel, a large page size will cause a performance problem. But in LiveGrid only the visible rows will be rendered. So it seems that the combination of LiveGrid and pagination will be the ideal solution.
Is it possible to have pagination in LiveGrid? If the total count is very large (greater than 10000), it will be hard to control the scroll bar to navigate to a particular record.
In normal GridPanel, a large page size will cause a performance problem. But in LiveGrid only the visible rows will be rendered. So it seems that the combination of LiveGrid and pagination will be the ideal solution.
AFAIK there is already an implementation of a buffered paging grid... might be wrong though... but I have written one for my company a while ago so it should not be too hard to do that. However, paging support is not planned for Livegrid.
Originally Posted by MindPatterns
I wonder what kind of BufferedGridView you're using, as the original version does not override the method "onHeaderClick"
Reply With Quote
