Re: [x3d-public] Definition of outputOnly field question

Of course... that was a bit silly of me, I must admit... just like touchTime field and others that do not change because of user intervention but some internal mechanism... thank you.

George

----- Original Message -----

From: Mirko Gontek

To: 'George Anastassakis' ; x3d-public@web3d.org

Sent: Monday, March 27, 2006 1:55 PM

Subject: AW: [x3d-public] Definition of outputOnly field question

hi george,

here is an example for how the value of an outputOnly field may be changed:

the 'isBound' field of viewpoint node is an outputOnly field. so you cannot change the value of 'isBound' directly. but its value changes when the inputOnly field 'set_bind' of the viewpoint is manipulated. also the value of the outputOnly field 'bindTime' will change:

"Sending a set_bind FALSE event removes the Viewpoint node from the stack and produces isBound FALSE and bindTime events."

hope this will help you.

mirko gontek

Von: owner-x3d-public@web3d.org [mailto:owner-x3d-public@web3d.org] Im Auftrag von George Anastassakis
Gesendet: Montag, 27. März 2006 12:16
An: x3d-public@web3d.org
Betreff: [x3d-public] Definition of outputOnly field question

There is something I don't understand as to the definition of outputOnly field access type in the specification (Part 1, Section 4 (Concepts)):

"outputOnly access, which means that the node may send an event when its value changes, but does not allow the field's value to be written"

So, if the field's value cannot be written, how can it change?

George