So let's say you have two views, v1 and v2, in a ViewStack. When you switch from v1 to v2, v1 fades out and v2 fades in. If in-between v1 is selected again, it should continue getting faded out? Should it also simultaneously fade in? How would that work?
Anyway. You'll have to override commitProperties() in a ViewStack subclass, copy all the code, and implement your own version of commitSelectedIndex() where you're not calling endEffectsStarted() on the children. On 4/23/07, João <[EMAIL PROTECTED]> wrote: > First, the example: > > http://www.riapt.org/opensource/viewstack_test2/viewstack_test.html > (com view source enabled). > > The application has one viewstack with three components, and three > buttons for the navigation. Each component has one hideEffect and one > ShowEffect. It works fine and smooth, except if we click very fast on > the navigation button, before the effects end. When this happens, the > effects are abruptly interrupted, something i do not wish. According > to the documentation: > > "The ViewStack or TabNavigator container waits for the hideEffect of > the child container being hidden to complete before it reveals the new > child container. You can interrupt a currently playing effect if you > change the selectedIndex property of the ViewStack or TabNavigator > container while an effect is playing." > > In my specific situation, i do not want this behavior. Is there any > solution? > > > Thanks, > > João Saleiro > > > > > -- > Flexcoders Mailing List > FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com > Yahoo! Groups Links > > > >
