I could be wrong, but I'm pretty sure fx are automatically queued.
Something John did about 2 months ago.
There's not a commit log for the actual queuing, but there is one for
a bug fix:
------------------------------------------------------------------------
r209 | john | 2006-08-16 19:38:34 -0700 (Wed, 16 Aug 2006) | 2 lines
Changed paths:
M /jquery/src/fx/fx.js
Fixed the issue with queued effects becoming corrupted.
------------------------------------------------------------------------
Corey
On Oct 9, 2006, at 9:13 AM, Abdur-Rahman Advany wrote:
> Sam,
>
> Yeh, but using queue's allows that events don't fire a fx during some
> other fx... I can't do that with callbacks...
>
> Sam Collett wrote:
>> On 09/10/06, Abdur-Rahman Advany <[EMAIL PROTECTED]> wrote:
>>
>>> Hi guys, I was searching if there was a way to do queuing like in
>>> script.aculo.us (I am switching to jquery but this is the only
>>> bump....)
>>>
>>> Here some doc's on how it works in script.aculo.us
>>> http://blog.railsdevelopment.com/pages/effect/queue/
>>>
>>>
>>
>> Have you tried using callbacks? they are fired whenever an effect
>> finishes.
>>
>> $("#mydiv").fadeOut("slow", function()
>> {
>> $("#mydiv2").fadeIn("slow");
>> })
>>
>> _______________________________________________
>> jQuery mailing list
>> [email protected]
>> http://jquery.com/discuss/
>>
>>
>
>
> _______________________________________________
> jQuery mailing list
> [email protected]
> http://jquery.com/discuss/
_______________________________________________
jQuery mailing list
[email protected]
http://jquery.com/discuss/
