Getting rid of the blink after a TranslateAnimation

by Mark » Fri, 11 Feb 2011 11:40:58 GMT


Sponsored Links
 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?

-- 



Re: Getting rid of the blink after a TranslateAnimation

by Hari Edo » Fri, 11 Feb 2011 22:50:18 GMT


 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.




-- 


Sponsored Links


Other Threads

1. Garmin audio powered car mount

Keren. ....gak kalah sama hp lokal, ada speaker optional
Itu berapa duit boss, konektor apart,pake battery

~ Jus69 ~
|| send using {*filter*} motoblurpowered by xl broadband ||




Untuk android a10.
Holder kok ada speaker ya.
speaker a10 udah keras suaranya ditambah ini pula.

photo in lowlight situation with hd7+photo enhancer

syd
ptk
-- 
===============
"

-- 
===============
"

2. Why does android native contact app have CACHED NAME,CACHED NUMBER TYPE and CACHED NUMBER LABEL ????

Hi,

   Android native Contact application maitaining different data bases
for Contacts and CallLog.

   Contact data base is having entire information about Contact.
   CallLog has information all Calls.


   Once CallLog Database is observed. The database is having
information about CallLog like
   Number,Duration,Date,Type,New etc.. along with Contact information
like CACHED NAME,
   CACHED NUMBER TYPE and CACHED NUMBER LABEL.

   These all are being maintained in Contact data base.
   Why again does android maintaining these in CallLog database?
   Is not there any problems like data base anomalies?
   Is this design because of performances issues?

   Please correct me if i am wrong?


   Any help would be great!!!





-- 

3. How to use one application GUI code as jar file from other appliaction?

4. Slider bar

5. Camera Hardware abstraction layer for froyo

6. Undeletable SMS

7. How to startActivity() in a subclass of Dialog?