Note that the usual matrix-manipulating animations don't change the hit-testing for a view, so you have to actually move the real view if you plan on animating a view that is touchable.
My app, "Qwiz - Hiragana", uses a LOT of drag and drop of views, and touchable views that move around on their own initiative. I implemented a true Animation class that adjusts the view's position instead of manipulating the drawing transform matrix. Then you don't need to reinvent the wheel of timing and iterating and interpolating things (and you can use all of the other fun iterators to bounce or wiggle the view). I use a FrameLayout to support moving things around by their margin coordinates, instead of an AbsoluteLayout, but the idea is the same. On Feb 10, 10:40 pm, Mark <markree...@gmail.com> wrote: > I'm using TranslateAnimation to actually move a View from one place > to another, however from what I can google no one has managed to > actually do this without having the View blink out for a second at the > end of the animation... If you've managed to do this without the > blink please share. > > Has anyone tried doing the translate themselves with AbsoluteLayout? > It looks like I'll have to duplicate the translate functionality by > using a Handler to act as a run loop and move the View myself? A > handler isn't a separate thread right? I just use it to to call a move > function every X ms? -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
