Mozart: Specify texture origin explicitly.

Mozart: Specify texture origin explicitly.

Previously we assumed the origin was always top-left but OpenGL
likes to create textures with the origin in the bottom-left.
Since we don't always get what we want in this life, let the client
specify what origin it used.  Maybe later we can grumble about it
and replace (or augment) this with a more general means of specifying
texture coordinates or texture matrices for rendering.

Flipping the node's coordinate system upside-down in Spinning Cube
has undesirable consequences on the input dispatch (since the events
get flipped too, as expected) so it was time to remove the old hack
and resolve the origin problem.

BUG=
R=abarth@google.com

Committed: https://chromium.googlesource.com/external/mojo/+/bae77abe00df82bc66c7febfba7b8c5104f96ec9

[jeffbrown, 2016-03-09 02:19:15]

jeffbrown@google.com changed reviewers:
+ abarth@google.com

[abarth, 2016-03-09 03:52:03]

LGTM

I guess this is better than picking a winner.

[jeffbrown, 2016-03-09 22:22:46]

Description was changed from

==========
Mozart: Specify texture origin explicitly.

Previously we assumed the origin was always top-left but OpenGL
likes to create textures with the origin in the bottom-left.
Since we don't always get what we want in this life, let the client
specify what origin it used.  Maybe later we can grumble about it
and replace (or augment) this with a more general means of specifying
texture coordinates or texture matrices for rendering.

Flipping the node's coordinate system upside-down in Spinning Cube
has undesirable consequences on the input dispatch (since the events
get flipped too, as expected) so it was time to remove the old hack
and resolve the origin problem.

BUG=
==========

to

==========
Mozart: Specify texture origin explicitly.

Previously we assumed the origin was always top-left but OpenGL
likes to create textures with the origin in the bottom-left.
Since we don't always get what we want in this life, let the client
specify what origin it used.  Maybe later we can grumble about it
and replace (or augment) this with a more general means of specifying
texture coordinates or texture matrices for rendering.

Flipping the node's coordinate system upside-down in Spinning Cube
has undesirable consequences on the input dispatch (since the events
get flipped too, as expected) so it was time to remove the old hack
and resolve the origin problem.

BUG=
R=abarth@google.com

Committed:
https://chromium.googlesource.com/external/mojo/+/bae77abe00df82bc66c7febfba7...
==========

[jeffbrown, 2016-03-09 22:22:48]

Committed patchset #2 (id:20001) manually as
bae77abe00df82bc66c7febfba7b8c5104f96ec9 (presubmit successful).