I don't understand enough of the animation and queuing system to make a descision, but if the change doesn't affect any published API, it should be fine.
Exposing jQuery's queuing system as a public API sounds very useful to me. Its already there anyway! Jörn On Thu, Oct 23, 2008 at 3:47 PM, Ariel Flesler <[EMAIL PROTECTED]> wrote: > > While working on the ultra chaining plugin mentioned on the > neighboring thread, I recall that $.fn.queue auto executes the sent > function if it's the first (and only) in the queue. > > This behavior is used for the fx module, so that one can queue > animations w/o worrying about keeping the queue running. > > The problem is, I'm heavily relying on $.fn.queue right now, but not > just for fx. Thing is, this behavior really complicates my code > because the "auto execute" behavior is meaningless for anything but > fx. > > If I queue a function, doesn't mean I want it auto executed. To work > around this, I'd have to push an empty function every time queue is > empty, but that's gross. Also, queue() is internal to jQuery so I > can't "overload" it. > > In short, may I change that behavior in the core, so that only fx > queues get auto executed ? It's not just a patch for my situation, I > think it applies to every other queue application but fx. > > Also... what about making queue accessible from the outside ? seems > like the same pattern as $.data. > > Cheers > -- > Ariel Flesler > http://flesler.blogspot.com > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en -~----------~----~----~----~------~----~------~--~---
