On Mon, Dec 7, 2009 at 15:57, Ken MacDonald <[email protected]> wrote:
> I had considered using a timer before querying the DB, since the only > request I really need to go to the server is the very last one, but I think > this depends on a variety of things I may not be able to control - keyboard > repeat rate, etc. I may yet get around to setting that up, but would still > like a way to notify the user that something is happening. I did try > changing the display panels and calling syncAppearance(), but it seems to > have no effect - is that the 'refresh' method you mention? 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? > 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 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? Derrell
------------------------------------------------------------------------------ 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
