hi everyone, it''s my first time tonight. great script lib you''ve got there. i spent a whole day trying to code myself, use tutorials, use dreamweaver timeline animation - when i was about knocked out by the heavy draw backs i stumbled upon this truly mir.aculo.us library and all i ever asked for became true! thanks! one question though: is it possible to disallow triggering new effects while one (the same) effect is running? best regards, hendrik frank
Yeah, but it''s a bit cumbersome atm. You can call on the effects with:
var myeffect = new Effect.Blah(...)
And then, before you initialize a new effect, do
if(myeffect.timeout) { // effect is still running, do effect.cancel()
to stop old effect }
or
if(!myeffect.timeout) { // effect is finished }
Note that making this easier is something i''ve on the list for a
future release, so stay tuned.
Also, I''d like to hear ideas and see use cases where this could be
helpful. There are three distinct possibilities I see here: 1) an
option to disallow any or specific Effects on a particual element
while the effect is running, 2) force cancelling the effect if a new
effect is run on the same element and 3) queueing up the effect to
wait for all the currently queued up effects on a particular element
having finished and starting only then (could be tricky if the
element was removed/changed by then).
Thomas
Am 11.08.2005 um 23:33 schrieb Hendrik Frank:
> is it possible to disallow triggering new effects while one (the
> same) effect is running?
>
> best regards,
> hendrik frank
> Am 11.08.2005 um 23:33 schrieb Hendrik Frank: > > > is it possible to disallow triggering new effects while one (the > > same) effect is running?On 8/12/05, Thomas Fuchs <thomas@fesch.at> wrote:> Yeah, but it''s a bit cumbersome atm... > Also, I''d like to hear ideas and see use cases where this could be > helpful. There are three distinct possibilities I see here: 1) an > option to disallow any or specific Effects on a particual element > while the effect is running, 2) force cancelling the effect if a new > effect is run on the same element and 3) queueing up the effect to > wait for all the currently queued up effects on a particular element > having finished and starting only then (could be tricky if the > element was removed/changed by then).A specific case where I ended up implementing my own solution to the problem was that of tooltips, where I had a tooltip fade on then fade off, triggered by hover events. The problem was noticeable when you quickly passed over an element, triggering Appear and Fade almost at the same time, causing a lot of flickering. -- Rob Sharp email/jabber: rob@sharp.id.au web: http://sharp.id.au pgp: 0E2C C63B BA04 DEB4 7CC0 84FD 17E3 6AA4 87FB 62DF