> I don't understand what you mean by changing the display panels. What > exactly are you trying to achieve? Preventing your remote request from being > issued except for the last one, or something else? > > I'd like to display something to tell the user that the app hasn't just 'frozen'. Even be able to display "Working...". Right now, as soon as the selection changes, the server request goes out, so stopping them isn't necessarily practical, but while the server requests trickle back in, I'd like to be able to display SOMETHING.
> Qooxdoo really seems to be "letting the dust settle" before applying any of >> the updates I've set, which is pretty frustrating. >> > > qooxdoo is doing exactly what it's supposed to do for the vast majority of > applications: updating the page with the most recent stuff when the > application becomes idle. > I'd like to display that the application is still doing something or other. When people select (in this case by scrolling down w/up or down-arrow) when they stop, they have to wait a minute or more before the display updates. I don't want to display every row, but I can't display ANYTHING. > I think, in your case, you're trying to do something different. Normally, > if you scroll through a table quickly, you don't want the browser to spend > the time updating each and every row; rather, you want it to just render the > visible rows once you stop pressing the arrow keys. Other than your remote > request, is there something else happening that follows a different > paradigm? > >
------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev
_______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
