Correction to Grnode comments...

[Lofton Henderson <lofton@rockynet.com>]

At 04:34 PM 4/21/2005 -0400, Benoit Bezaire wrote:
>[...]
>3.2.1.5 Grnode
>   - Fix Description to (minor errors): The application structure
>   'grnode' is meant to group basic graphical primitives only. For this
>   reason, 'grnode' must contain the APS 'id' parameter required by
>   CGM:1999 for all APS. 'id' is the only APS attribute allowed on a
>   'grnode'.

Although it behaves like one, 'id' is not an APS attribute, it is a 
parameter of the APS element (historical baggage of CGM:1999).

Correct:
BegAps  "myApsId" "grnode" Statelist;
BegApsBody
...etc...

Incorrect:
BegAps  "grnode" Statelist;
ApsAttr  "id" "14 1 ""MyApsId""";
BegApsBody;
...etc...

All the rest is okay and I applied it...

>The content of a 'grnode' is the same as for the
>   'grobject' Application Structure.
>
>   Even if 'visibility' and 'interactivity' are not allowed on the APS,
>   the 'grnode' supports inheritance (i.e., it is possible to make a
>   'grnode' visible or non-visible by inserting it within an object
>   which support the 'visibility' attribute).
>
>   - Fix Viewer Behavior to (minor errors): Unlike other application
>   structures, 'grnode' is not interactive; i.e., it does not receive
>   mouse events. The content of a 'grnode' can however be interactive
>   if it is a direct child of a 'grobject', 'para' or 'subpara'.
>   Additionally, if a mouse event is triggered on the geometry of a
>   'grnode', an ancestor node, if of type 'grobject', 'para' and
>   'subpara', instead responds to the event. See the Event interface
>   for more information regarding mouse events.

-Lofton.