Fixed
Status Update
No update yet.
Comments
il...@google.com
Jeremy, is this still an issue? I think the problem was that you had two transitions targeting the same View for the same action (e.g. two Slide() transitions).
ap...@google.com
I have a similar issue with plain AnimatorSet:
set.start()
set.pause()
set.setCurrentPlayTime(100)
set.setCurrentPlayTime(0)
set.setCurrentPlayTime(100)
set.resume()
doesn't play animation in resume().
il...@google.com
Should clarify that if I filter out setCurrentPlayTime(0) (or replace it with setCurrentPlayTime(1)) it works well.
Also even with setCurrentPlayTime(0), onAnimationEnd is notified with correct delay (as if the animation has played).
Description
Version used: 1.1.0-alpha09
Not sure why you're doing this, but there's a back pressed listener being added to the dispatcher in the initializeChildFragmentManager method, which itself is only called in performOnCreateView. Why isn't the child fragment manager just instantiated when the fragment is first initialized? There are so many bugs around this. Anyway, this means any back pressed listener added in the Fragment's onCreate is essentially pointless since it will always be overridden by the fragment manager's one which pops the back stack. However, back pressed listeners added in onViewCreated work since they're after the FM's listener.