Right - time to deal with all these helpful answers I've been getting, but
first, to save time, let me say... it's fixed! And a very simple fix it was
too, which I /thought/ I'd already tried...
On 29 Sep 2011, at 17:15, Richard Quadling wrote:
Create a test case where it goes wrong. Write new
On 30 September 2011 10:27, Chris Sansom ch...@highway57.co.uk wrote:
Right - time to deal with all these helpful answers I've been getting, but
first, to save time, let me say... it's fixed! And a very simple fix it was
too, which I /thought/ I'd already tried...
On 29 Sep 2011, at 17:15,
On 30 Sep 2011, at 12:32, Richard Quadling wrote:
onFailure / onSuccess is in response to a working result from the AJAX call.
onComplete is in response to the AJAX mechanism shutting down.
onComplete will always be called, but it isn't its job to deal with
the data from the call. That is
On 30 September 2011 12:53, Chris Sansom ch...@highway57.co.uk wrote:
On 30 Sep 2011, at 12:32, Richard Quadling wrote:
onFailure / onSuccess is in response to a working result from the AJAX call.
onComplete is in response to the AJAX mechanism shutting down.
onComplete will always be
I never meant to imply that onComplete did the same thing as onSuccess, what
I meant to state was that onComplete ALWAYS gets called last. onSuccess can
always set a flag and onComplete can do the UI updates right before turning
off the spinner. This is useful if you're experiencing those
On Sep 30, 3:58 am, Marty Amberg mar...@edenstreet.com wrote:
Might have been asleep during my previous google searches but I found
tj's sitehttp://proto-scripty.wikidot.comtoday which seems like
answers questions of what I would want and think prototype needs to
grow. No sense in
On 30 September 2011 13:09, Phil Petree phil.pet...@gmail.com wrote:
I never meant to imply that onComplete did the same thing as onSuccess, what
I meant to state was that onComplete ALWAYS gets called last. onSuccess can
always set a flag and onComplete can do the UI updates right before
