OK, sorry, my mistake, not the remote table model's: the LIMIT part of 
an sql query is  NOT LIMIT firstrow, (lastrow-firstrow) but LIMIT 
firstrow, (lastrow-firstrow+1) ...  I need to get more sleep...C.


Christian Boulanger schrieb:
> Actually, I think it does prefetch the data ok - my block size is 50 and it
> will always fetch 50 ahead and load it in the background  - except, of
> course, when I make a big jump into areas of the data where there has been
> no preloading yet. However, what seems to be happening is that it always
> skips one row when prefetching. I have to find out whether it is the backend
> that does that or if my use of the remote table model is the problem...
>
>
>
> Derrell Lipman wrote:
>   
>> On Feb 12, 2008 5:00 PM, Christian Boulanger <[EMAIL PROTECTED]> wrote:
>>     
>>> Thanks Derrell,
>>>
>>> it is definitively not working this way:
>>>
>>> tableModel.reloadData();
>>> table.setFocusedCell(0,0,true);
>>>
>>> as you said, it probably has to be done AFTER the data is loaded. Since
>>> the
>>> table retrieval is behind-the-scenes in the remote model,  I have to
>>> figure
>>> out how to differentiate "reloads" from "new loads" somehow.
>>>       
>> The table retrieval is "behind the scenes" but done by your class that
>> extendes qx.ui.table.model.Remote.  How about calling it from your
>> _loadRowData() method, just after you've called _onRowDataLoaded() ?
>> Alternatively, since _onRowDataLoaded() will be dispatching a
>> "dataChanged" event, you can just listen for that and issue your
>> setFocusedCell() call there.
>>
>>     
>>> A different question. As you can see at
>>> http://rsoz.rewi.hu-berlin.de/~baer/bibliograph/frontend/build/ , when
>>> using
>>> the mouse scroll wheel or other ways of quickly skimming the large
>>> datasets,
>>> there is often some gaps in the data. They disappear when I do a
>>> reloadData
>>> on the current position.
>>>
>>> I wonder: is this my mistake or a problem with the remote table model?
>>> Has
>>> anyone else the same problem?
>>>       
>> Since synchronous requests are dangerous and block the entire browser,
>> it is very possible that scrolling can happen while there is no data
>> yet available.  In fact, I recently noticed that the current design
>> doesn't have rows be "prefetched" until they're actually trying to be
>> updated on the screen.  I hope to find an earlier place to prefetch
>> data from, which should greatly help that problem.
>>
>> Derrell
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Microsoft
>> Defy all challenges. Microsoft(R) Visual Studio 2008.
>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>> _______________________________________________
>> qooxdoo-devel mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>
>>
>>     
>
>   


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to