[x3d-public] MatrixTextureTransform node

[Andreas Plesch]

The existing TextureTransformMatrix3D node is identical to the
MatrixTextureTransform we had discussed, except for the name and the
component it belongs to.

This means there is no need for a new MatrixTextureTransform node.

There may be a case for renaming the existing node and moving it to the
Texturing component.

-Andreas



---on the phone---

On Thu, Oct 24, 2019, 7:00 PM Brutzman, Donald (Don) (CIV) <brutzman at nps.edu>
wrote:

> Examples please, colleagues... theory always goes better with practice.
>
> On 10/24/2019 1:51 PM, Andreas Plesch wrote:
> >> Date: Thu, 24 Oct 2019 19:25:41 +0200
> >> From: Holger Seelig<holger.seelig at googlemail.com>
> >> To:x3d-public at web3d.org
> >> Subject: Re: [x3d-public] MatrixTextureTransform node
> >> Message-ID:<adfacda1-5243-3e78-1dfd-9d6b2d038b2e at gmail.com>
> >> Content-Type: text/plain; charset=utf-8; format=flowed
> >>
> >> What about TextureTransformMatrix3D
> >>
> http://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-WD1/Part01/components/texture3D.html#TextureTransformMatrix3D
> > That's it ! It just might make sense to get rid of the 3D reference
> > since it can also be used for 2d texture coordinates.
> >
> > -Andreas
>
> all the best, Don
> --
> Don Brutzman  Naval Postgraduate School, Code USW/Br
> brutzman at nps.edu
> Watkins 270,  MOVES Institute, Monterey CA 93943-5000 USA   +1.831.656.2149
> X3D graphics, virtual worlds, navy robotics
> http://faculty.nps.edu/brutzman
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20191025/6d459fbb/attachment.html>