How to turn off the popping fractal transcriptions to the back stack, I'm having trouble using it, custom animations especially , I hope this calls "out" animation, but it does not seem like
I have a simple way of handling a piece transaction (piece transaction), where I add a piece And apply a custom transition so that this fee Defense-in / get feed-out. I am also adding it back to the stack so that the user can undo the transaction with the button back, so that the segment can be navigated in the state before being added. Everything works great progress, but when the user clicks the back button, the transition animations do not reverse. What did I expect when the piece was removed, then it would use fade animation. Instead it is popping out (without animation) and then fades in the container. I'm not sure what this is happening, but this piece definitely does not fade. My application uses Compatibility Libraries to add piece support, but I agree to apply it to Honeycomb (Android-11). Does anyone know if I am doing something wrong here or if I am hoping too much? Ideally, I want to animate the pieces in the same way as how gmail (on the x-ray) is done by clicking on a message and then proceeding using the back button. Preferably not to override the functionality of the back button and after maintaining the status of its own piece, I can have several "transactions" from which I want to come back and I'm not a fan of the recovered wheels. The bug was released in 3.2 The following was added with the following API: It is worth noting that it has not yet been sent back to the compatibility library (as mentioned in the bug report). Protected Zero Change Changes () {Fragment Transaction Feet = FM. BBT transactions (); Ft.setCustomAnimations (android.R.anim.fade_in, android.R.anim.fade_out); Ft.add (R.id.fragment_container, New TestFragment ()); Ft.addToBackStack (zero); Ft.commit (); }
Comments
Post a Comment