ViewPropertyAnimator is optimized to perform animations. It's not meant to be used to discreetly set properties.
On Thu, May 24, 2012 at 11:26 AM, David Ozersky <[email protected]> wrote: > Hi Romain, > > Thanks for getting back to me...but I addressed my question to > "Droids"...and you make "Droids"...does that you make you some kind of > alien? :) > > Here is the other implementation I am thinking of > > ------------------------------------------------------------------------------------- > ...ACTION_MOVE > > ... get view, set new layout params, change properties etc > > invalidate() > ------------------------------------------------------------------------------------- > > I'm not sure exactly how the ViewPropertyAnimator works under the hood, but > it looks like there is a lot going on, and the manual approach would > probably be more efficient. But if it's a marginal improvement, I'd rather > use the property animation. > > Thank you..whatever you are! > > On Thu, May 24, 2012 at 1:27 PM, Romain Guy <[email protected]> wrote: >> >> ViewPropertyAnimator is designed and implemented to be *faster* than >> animating multiple properties with ObjectAnimator, etc. Note that it >> only makes sense if you're animating the values. >> >> On Thu, May 24, 2012 at 10:22 AM, duadinam <[email protected]> >> wrote: >> > Hi Droids, >> > >> > I'm a newbie developer working, looking for some advice. >> > >> > I'm working on a project with a custom drag and drop, and we can't use >> > the >> > drag and drop framework. However, many properties will be changing at >> > once. >> > I'm looking into using the ViewPropertyAnimator setX & setY function and >> > applying them in an onTouchEvent, or changing the margins in >> > LayoutParams >> > for the View and invalidating it. >> > >> > From my research, the ViewProperyAnimator looks like it should be worse; >> > however, I thought the difference in performance might be less >> > significant >> > when you're changing multiple view properties at the same time. >> > >> > What do you think? >> > >> > Thank you >> > David >> > >> > -- >> > You received this message because you are subscribed to the Google >> > Groups "Android Developers" group. >> > To post to this group, send email to [email protected] >> > To unsubscribe from this group, send email to >> > [email protected] >> > For more options, visit this group at >> > http://groups.google.com/group/android-developers?hl=en >> >> >> >> -- >> Romain Guy >> Android framework engineer >> [email protected] >> >> -- >> You received this message because you are subscribed to the Google >> Groups "Android Developers" group. >> To post to this group, send email to [email protected] >> To unsubscribe from this group, send email to >> [email protected] >> For more options, visit this group at >> http://groups.google.com/group/android-developers?hl=en > > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en -- Romain Guy Android framework engineer [email protected] -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
