[x3d-public] X3D minutes, 17 JAN 2020: visible field and X3DBoundedNode

[John Carlson]

Thanks don, I think this clarified my confusion over invisible transforms
and collisions.

On Mon, Jan 20, 2020 at 8:00 PM Don Brutzman <brutzman at nps.edu> wrote:

> Update summary:
> - (v4.0) add visible field to X3DBoundedObject, Mantis 1271
>    https://www.web3d.org/member-only/mantis/view.php?id=1271 (no longer
> named 'hidden')
>
> Preceding mail threads, summarized in Mantis:
>
> * As node list kept getting longer, realized X3DVisibleObject same as
> X3DBoundedObject.
>
> http://web3d.org/pipermail/x3d-public_web3d.org/2020-January/011673.html
>
> * Confirmed by Andreas as implemented in InstantReality: refactor visible
> field as part of X3DBoundedObject, 37 nodes total.
> * http://web3d.org/pipermail/x3d-public_web3d.org/2020-January/011674.html
>
> Test scene available:
> * X3D Example Archives: X3D for Advanced Modeling, Animation, Visible
> Shapes Test
>    "Test scene for visible field on X3DBoundedObject nodes, which is new
> to X3Dv4."
>
> https://x3dgraphics.com/examples/X3dForAdvancedModeling/Animation/VisibleShapesTestIndex.html
>
> https://x3dgraphics.com/examples/X3dForAdvancedModeling/Animation/VisibleShapesTest.x3d
>
> New refinement:
> - (v3.2+) CollisionCollection implements X3DChildNode, not X3DNode
> - (v4.0) CollisionCollection contains nodes with X3DBoundedObject
> interfaces, so
>    TODO CollisionCollection needs to be marked in specification as
> X3DBoundedObject as well.
>    now recorded as issue 1275
>    https://www.web3d.org/member-only/mantis/view.php?id=1275
>
> On 1/17/2020 9:34 AM, Don Brutzman wrote:
> > [...]
> > > 4.a. Mantis 1271: add hidden field to Shape
> >       https://www.web3d.org/member-only/mantis/view.php?id=1271
> >
> > Discussion:  see email thread from last week's minutes and the Mantis
> issue itself.
> >
> > Pending today: rename to "visible"?  Note change to CADAssembly.  Also
> need example scene.
> >
> > TODO: example models for testing implementations.
> >
> > Related: whether this has impact on X3DPickableNode.  Our immediate
> reaction is to confirm that we have formal prose that non-visible geometry
> is not pickable.
> >
> > We agreed to proceed in this manner.  Once accomplished, this bug is
> left open that final implementation/evaluation in 2 browsers is needed.
>
>
> 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
>
> _______________________________________________
> x3d-public mailing list
> x3d-public at web3d.org
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20200121/fc683531/attachment.html>