Yes, thought crossed my mind as well for something like that. Perhaps a common type of JS queue could be made for this, as I would not be surprised if this functionality is revisited elsewhere. Something like a non-duplicate PPR list, when a new event is added, the previous is removed and each event has a timeout associated with it (fire after x millis).
On 9/21/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: > true, > > perhaps we can include TRINIDAD-730 as well. > > Like, after 1000 ms start with the "loop" of increase / decrease and > inside the loop, > every 100 ms, do an update. Once the "loop" get's its time-out, fire > the change event, for the spinbox. > > does that make sense ? > > -M > > On 9/21/07, Andrew Robinson <[EMAIL PROTECTED]> wrote: > > Is this a good idea? > > > > If the user wants to increase the counter 5 times, you would not want > > 5 ajax calls for every time they click the up arrow. > > > > -Andrew > > > > On 9/21/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: > > > Hi guys, > > > > > > I added a patch (and a comment) to TRINIDAD-729 (see [1]). > > > I am not sure if there is an issue with this fix/patch. > > > Do you mind to review it ? > > > > > > Thanks! > > > Matthias > > > > > > [1] https://issues.apache.org/jira/browse/TRINIDAD-729 > > > > > > -- > > > Matthias Wessendorf > > > > > > further stuff: > > > blog: http://matthiaswessendorf.wordpress.com/ > > > mail: matzew-at-apache-dot-org > > > > > > > > -- > Matthias Wessendorf > > further stuff: > blog: http://matthiaswessendorf.wordpress.com/ > mail: matzew-at-apache-dot-org >
