I tried putting the morph calls in parallel and it really just changed the responsiveness of the rollover affect making it more 'stiff' and less fluid when multiple menu items were selected in succession.
The affect i am trying to get it achieved by my first script (currently running on the test page), the only problem is it seems that the computer loses track of which order the morphs are called in. ex: when new morphs are called on dividers already in a morph process, it seems to overwrite the current morph with the new one, the new morph completes, then the divider flashes white as if it was still running the original morph command in the background and you just see the final result after the secondary overwriting morph has finished. im not sure if this is actually what is going on, its just the best way i can think of to explain the situation. it almost seems like a queue is required to ensure that the morphs complete in the proper order, and are canceled and re-ordered as the menu item selection changes, or maybe just canceling the previous morph on an element before ordering the new one (if that is not automatically done by javascript).. any one have any ideas/experience working with complex multiple morphing situations like this, or perhaps offer an alternative to using morph to complete the effect i want to achieve.. 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en.
