You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 14, 2018. It is now read-only.
Usually we construct animators starting with a call to e.g. ValueAnimator#ofXY, continuing with configuration in builder style - because the api allows it. Until now, and also with the current KTX implementation, this builder would get broken as soon as we want to attach an AnimatorListener (or even an AnimatorUpdateListener for ValueAnimator), making code look super ugly.
Instead of returning the AnimatorListener that we passed in the very same statement (which makes it kinda redundant), we could return the function receiver, the Animator we're adding our listener to, in order to maintain builder flow.
The text was updated successfully, but these errors were encountered:
Usually we construct animators starting with a call to e.g. ValueAnimator#ofXY, continuing with configuration in builder style - because the api allows it. Until now, and also with the current KTX implementation, this builder would get broken as soon as we want to attach an AnimatorListener (or even an AnimatorUpdateListener for ValueAnimator), making code look super ugly.
Instead of returning the AnimatorListener that we passed in the very same statement (which makes it kinda redundant), we could return the function receiver, the Animator we're adding our listener to, in order to maintain builder flow.
The text was updated successfully, but these errors were encountered: