[x3d-public] PlaneSensor x_changed output event

d vv dan.vera at gmail.com
Thu Sep 8 09:46:55 PDT 2016


I can see real value in that too.
As said, this would indeed allow avoiding a lot of scripting I complex ui
design.
Daniel

On 7 Sep 2016 11:07 p.m., "Yves Piguet" <yves.piguet at gmail.com> wrote:

> Might be easiest to do additional 'extension fields' (for new specs?) to a
> few sensor nodes so as not to break old scenes:
> SFFloat scalar_changed
> Or add utility nodes in a new Utility Component for splitting SFVec3f,
> SFRotation into scalars?
>
> Linesensor
> x I didn't implement the translation_changed as sffloat (sfvec3f like
> planesensor)
>
> PointSensor
> - yes, plane perpendicular to view, at distance where pick ray hits
> affected geometry
>
> -Doug
>
> > ________________________________________
> > From: Yves Piguet <yves.piguet at gmail.com>
> > Sent: September 8, 2016 12:24 AM
> > To: doug sanden
> > Cc: X3D Graphics public mailing list
> > Subject: Re: [x3d-public] PlaneSensor x_changed output event
> >
> > I'd also thought about a LineSensor node. I don't really have a strong
> preference between LineSensor and x_changed in PlaneSensor, provided that
> the output of LineSensor is an SFFloat, not an SFVec3f. The advantages of
> x_changed are (1) simpler change to specs and implementations, and (2)
> easier to generalize to an angle_changed in CylinderSensor node (scalars in
> SphereSensor aren't very useful without further processing anyway).
> >
> > I'm not sure to understand your PointSensor. There must be some
> projection from 2D mouse position to a value with 1 or 2 degrees of
> freedom. Is it implicitly a plane perpendicular to the view direction? It
> might solve other problems, but not what I'm trying to address: obtaining a
> scalar value from a VR slider without obfuscating the x3dv file with
> trivial scripts and routes.
> >
> > Yves
> >
> > Le 8 sept. 2016 à 00:35, doug sanden a écrit :
> >
> > >
> > > Somewhat related: proposed PointSensor node
> > > I found LineSensor (not in specs, did as experiment) would do some of
> the work of PlaneSensor > trackpoint_changed for dragging axis handles. And
> extrapolating from that when playing with a X3DConnector prototype, I
> thought there should be a PointSensor node. Then you don't need trackpoint
> changed because the main output from PointSensor would be doing that job,
> except more explicitly and reliably.
> > > http://dug9.users.sourceforge.net/web3d/tests/JohnCarlson/
> x3dconnector.x3d
> > > - problem with planesensor: for general 3D sensing, as you move around
> the object to drag from an orthogonal axis, you could be looking edge-on at
> the planesensor. Similar to problem dragging axes handles with planesensor,
> solved with LineSensor.
> > >
> > > ________________________________________
> > > From: x3d-public <x3d-public-bounces at web3d.org> on behalf of Yves
> Piguet <yves.piguet at gmail.com>
> > > Sent: September 7, 2016 4:05 PM
> > > To: X3D Graphics public mailing list
> > > Subject: [x3d-public] PlaneSensor x_changed output event
> > >
> > > Hi,
> > >
> > > I'm investigating ways to simplify scenes. To avoid some scripts, I
> propose to add scalar output events to PlaneSensor: in addition to its
> existing trackPoint_changed and translation_changed output events, it would
> also have x_changed and y_changed, of type SFFloat. Likewise an SFFloat
> angle_changed could be added to CylinderSensor.
> > >
> > > What do you think?
> > >
> > > Yves
> > >
> > >
> > > _______________________________________________
> > > x3d-public mailing list
> > > x3d-public at web3d.org
> > > http://web3d.org/mailman/listinfo/x3d-public_web3d.org
> > >
> > > _______________________________________________
> > > x3d-public mailing list
> > > x3d-public at web3d.org
> > > http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>
>
>
> _______________________________________________
> 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/20160908/4a1766ab/attachment-0001.html>


More information about the x3d-public mailing list