[x3d-public] [x3d] Spec Comment by on 19775-1: Abstract X3D Definitions - V3.3: X3DPickSensorNode matchCriterion

[Don Brutzman]

Thanks for a great specification comment Doug, very helpful.  Yes all concrete nodes implementing the X3DPickSensorNode abstract object type should include the matchCriterion field.

I checked X3D DTD, XML/JSON Schemas and Tooltips.  All include matchCriterion satisfactorily.

Saw a further small improvement, TODO: refactor various enumeration values for X3DPickSensorNode to allow independent referencing in X3D Object Model.

Happy New Year!  8)


On 12/30/2016 2:44 PM, Spec Feedback wrote:
> Comment on 19775-1: Abstract X3D Definitions - V3.3
> 38.3.2 X3DPickSensorNode
> http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/picking.html#PickableGroup
>
> -----------------
> SFString [in,out] matchCriterion   "MATCH_ANY"
> ["MATCH_ANY"|"MATCH_EVERY"|"MATCH_ONLY_ONE"]
> matchCriterion is given in the Abstract section, but none of the concrete
> PickSensor node types show the field, normally in the web3d specs the
> concrete node types list all the fields from the abstract type they inherit
> from.
> - not hard to implement in concrete nodes, so can't see a reason they aren't
> in the concrete nodes
> -----------------
>
> Submitted on Friday, 2016,  December 30 - 2:44pm
> by  (Doug Sanden )
> IP: 172.219.44.134
>
> See: http://www.web3d.org/node/1694/submission/1157

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