Thanks for looking into it Matias. Yeah the only thought I had as a work around is if there was a way to wait for a digest to complete prior to calling the $state.go. I haven't dug into it too much as it felt like a hacky work around.
Gordon On Friday, March 28, 2014 2:16:09 AM UTC-5, Matias Niemelä wrote: > > Hey Gordon. > > From what I can see with your example is that the problem occurs when you > switch between left and right (or press toggle classes). The old view still > uses the former class value and *does not update *when the class value > toggles. This is because the leave animation (just before starting) > destroys the scope of the view. The ng-class change doesn't update in time > because the view changes first and then the class value. > > I'm not having any luck fixing this in a clean way within your example. > Perhaps ui-view as well as ngView can be changed to destroy the scope after > the first digest has run (since by that time ngClass will have fully > resolved itself and ngAnimate will still behave the same since it too is > not triggered until after the digest). > > I will open create a demo tomorrow with ngView and open an issue on Github > if the result is the same as with ui-view. > > On Tuesday, March 25, 2014 12:54:09 PM UTC-4, Gordon Bockus wrote: >> >> Hello, >> I'm working on a wizard style page where I want to have a previous/next >> buttons to navigate from step to step. I'm using the ui-router and >> animation to add the sliding effect. The problem I've run into is >> reversing the animation direction. When the user clicks the previous >> button the current view uses the wrong direction class for exit. I added a >> toggle button and if that is clicked then the previous button the animation >> is correct. I forked the ui-router animation example to demonstrate. >> http://plnkr.co/edit/kSsW9T?p=preview >> It seems I'd need to alter the button handler to allow digest loop after >> altering the scope to drive the animation class change, then calling the >> state transition. Any thoughts on the cleanest way to do this are >> appreciated. >> >> FWIW I also created an example using the standard router and it works out >> of the box: http://plnkr.co/edit/APFNx7jyfBCCmwunfOg5?p=preview >> >> Thanks, >> Gordon >> > -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
