Perhaps this is just a limitation, but I think what needs extending is
an option to not start effects at all till the queue is fully setup,
then the application should be able to just run the effect.queue. A
problem example here as shown,

        $$('div.steams div').invoke('hide').each(function(el)
                el.grow({transition: Effect.Transitions.spring, direction: 
center', duration: 1, queue: {position: 'end', scope: 'steam'}});
        new Effect.Event({ afterFinish: this.initializeMenu, queue:
{position: 'end', scope: 'steam'}});

the last Event Effect is not added to the steam queue, but is just run
concurrently - possibly in a new queue of its own.

Thanks Luke Parry

You received this message because you are subscribed to the Google Groups 
"Prototype &" group.
To post to this group, send email to
To unsubscribe from this group, send email to
For more options, visit this group at

Reply via email to