Hey joe t., i was just coming here to reply that i solved the problem
using the queue functionality of script.aculo.us. I created a separate
queue for each divider and simply clear all morphs before adding a new
one, so there is never the possibility of a morph finishing after its
been overwritten.

That is a good point regarding the CPU cycles issue (as i have noticed
from time to time with testing), but for the sites purpose i am not
too worried about this as there is no other real high-demand
functionality involved.

Thanks

-- 
You received this message because you are subscribed to the Google Groups 
"Prototype & script.aculo.us" group.
To post to this group, send email to prototype-scriptacul...@googlegroups.com.
To unsubscribe from this group, send email to 
prototype-scriptaculous+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/prototype-scriptaculous?hl=en.

Reply via email to