Tom and Christophe, thanks very much for your help. I've set up a test page here:
http://www.autonoetic.com/dev/test/effectQueueTest.html All my custom javascript is inside that page's source. I'm using the element id as the scope for the queue, as suggested, and calling all effects with 'new'. The effect still seems to be the same; though it's tough to say exactly what's happening, I only see the Grow effect. Let me know what you think, and thanks again. -Jay On Apr 18, 2:30 am, Christophe Porteneuve <[EMAIL PROTECTED]> wrote: > Hey Jay, > > Use the "new" operator for creating your effects, otherwise they won't > be able to run properly when combined. As for the queues, you *should* > use a custom queue indeed, instead of the global queue. But then, you > need not only the position, but also the scope (the name of the queue). > > Here's a per-element queue that should work: > > Effect.myEffect = function(elt) { > new Effect.Grow(elt, { direction: 'top-left', duration: 5, > queue: { scope: elt.id, position: 'end' }); > new Effect.Pulsate(elt, {queue: { scope: elt.id, position: 'end' }); > > } > > -- > Christophe Porteneuve a.k.a. TDD > "[They] did not know it was impossible, so they did it." --Mark Twain > Email: [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" 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/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
