Use PointF for 2-dimensional float values rather than Float[].
ClosedPublic

Authored by markwei on Apr 6 2017, 2:59 PM.

Diff Detail

Repository
rMDMSTREAMSANDROID reactive-motion-android
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.
markwei created this revision.Apr 6 2017, 2:59 PM
Restricted Application added a reviewer: O2: Material Motion. · View Herald TranscriptApr 6 2017, 2:59 PM
Restricted Application added a project: Material Motion. · View Herald Transcript
Restricted Application added a reviewer: O6: Material Android platform reviewers. · View Herald Transcript
Restricted Application added a reviewer: Material Motion. · View Herald Transcript
Restricted Application failed to build Restricted Buildable!Apr 6 2017, 3:01 PM
featherless accepted this revision.Apr 8 2017, 8:11 PM
featherless added a subscriber: featherless.

Awesome. Are there negative ramifications to this?

This revision is now accepted and ready to land.Apr 8 2017, 8:11 PM

Awesome. Are there negative ramifications to this?

Only thing I can think of is that PointF looks "awkward" in some cases. For example, an interaction whose value is a 2D translation would use PointF even though the translation is more of a "vector" than a "point".

This revision was automatically updated to reflect the committed changes.