[x3d-public] BooleanFilter inputFalse output value true or false ?

[Andreas Plesch]

Hi Michalis,

thanks, that's great. I guess it is just necessary to use a few more nodes
and routes.

Once IntegerTrigger becomes available for x3dom, I will adjust the test
scene.

Since three browsers (castle, x3dom, instantreality) implement the 'render'
field for Shape, it may become a candidate for the spec. ?

-Andreas

On Sat, Sep 16, 2017 at 11:13 AM, Michalis Kamburelis <
michalis.kambi at gmail.com> wrote:

> 2017-09-16 1:34 GMT+02:00 Andreas Plesch <andreasplesch at gmail.com>:
> > This is pretty standard x3d except for use of the x3dom 'render' SFBool
> > field which can be used to control rendering of a shape node. Is there a
> > standard conforming way to use a SFBool event to control rendering ?
> > 'render' is certainly convenient.
>
> The standard way to use SFBool to control rendering:
>
> - use 1 BooleanFilter, and connect it's inputFalse and inputTrue to 2
> different IntegerTrigger nodes,
> - each IntegerTrigger generates different integer value (they ignore
> their input boolean value),
> - both IntegerTrigger nodes connect to a single Switch.whichChoice.
>
> A working example in the attachment, tested on view3dscene, in classic
> and XML encoding for convenience.
>
> Caveats:
>
> - This switches not only visibility, but also collisions of your
> object, unlike the "render" field. You have to use Collision node if
> you want to tweak it.
> - It uses the BooleanFilter node, which is the very node you're trying
> to test :)
>
> I agree that "render" is useful, that's why view3dscene also
> implements it :)
> https://castle-engine.sourceforge.io/x3d_implementation_shape_
> extensions.php
>
> Regards,
> Michalis
>



-- 
Andreas Plesch
Waltham, MA 02453
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20170916/db3c2065/attachment.html>