[x3d-public] [...] set_Value prefix and value_changed suffix, potential v4 issue

Michalis Kamburelis michalis.kambi at gmail.com
Mon Apr 24 07:06:55 PDT 2017


2017-04-24 15:38 GMT+02:00 Andreas Plesch <andreasplesch at gmail.com>:
> But these are input_only and output_only fields, not inputoutput fields.
> Here is the spec. follows (satisfyingly) its own recommendation from 4.4.2.2
> Field Semantics, items h) and j).
>

Reading the Andreas mail, I realized that my testing

  ROUTE MyTimeSensor.fraction TO MyPositionInterpolator.fraction

vs

  ROUTE MyTimeSensor.fraction_changed TO MyPositionInterpolator.set_fraction

was not very useful: there is no inputOutput called "fraction" here,
so it's normal that the 1st form doesn't work.

The correct testcase of the question "is set_/_changed required to
refer to inputOutput fields as events" is to compare:

  ROUTE MyTimeSensor.isActive TO MyLight.on

vs

  ROUTE MyTimeSensor.isActive TO MyLight.set_on

Here, we test X3DLightNode.on (inputOutput field). A simple testcase
using this is attached.

Testing on my own view3dscene, we support both forms. So it looks like
I was wrong (two times!):

1. "Me from the past" understood the specification to mean "the
set_/_changed are *optional* if you want to refer to inputOutput field
as event". Just like it is more sensible to Andreas.

2. "Me from the past" implemented view3dscene to make them optional.

Sorry for the confusion:)

Regards,
Michalis
-------------- next part --------------
A non-text attachment was scrubbed...
Name: are_set_changed_optional_correct_test.x3dv
Type: model/x3d+vrml
Size: 326 bytes
Desc: not available
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20170424/5b439333/attachment-0001.x3dv>


More information about the x3d-public mailing list