Well .. why don't you let the server-feedback trigger your event instead of looping and waiting ... the XHR Request can evaluate Javascript e.g. and you could easily send some fireevent, depending on the server-feedback or a general onSuccess event function that, dependant on the feedback, triggers the event or a list of events.
I am a Designer myself and i can't see a reason for what your designer needs - everything on a website can be event triggered IMHO. On 4 Apr., 21:35, Sanford Whiteman <sa...@cypressintegrated.com> wrote: > > what do you mean with a true __getter__? instead of a 'false' one I > > mean? > > what do you mean with a true __getter__? instead of a 'false' one I > > mean? > > An actual ECMAScript getter which is called every time a property is > accessed. So you can detect unacceptably tight loops checking the > flag. Obvs. a fake getter (get() method) serves a similar purpose, > but a getter is more elegant IMO. > > -- S.
