Re: Question about paginated browsing



- A better solution is to count how many elements are you getting. For
instance, if you ask 30 elements and you only get 10, it's clear that in
the server it remains only 10 elements (if there were more, it would try
to satisfy your full request). So in this case you can hide the "more
elements" option.

This is similar to what I tried to describe. However, if I ask for
10 elements and I get 10 elements, then I don't really know if (1)
there are more elements or (2) that 10th element was really the final
element, right?

I think the result is that if things align right (or "wrong"), then the
application will provide a "more" menu entry when, in fact, there are
no more elements to receive.

I suppose an alternative would be to do a quick one-element browse just to
check for more. I had considered that, but thought it seemed a bit kludgey.

Am I still missing something?

Thank you,

-- 
Mike

:wq


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]