Re: [x3d-public] Using TimeSensor+PositionInterpolator with SAI

[Alan Hudson <giles@yumetech.com>]

Bradley Vender wrote:
> I decided to work through the bug case to see what was going on, and 
> what's happening is that there is a set1Value call on 'addChildren'. The 
> current set1Value methods are implemented to perform in the same manner 
> that user code would:
>   1.  read the old field value
>   2.  change one or more values
>   3.  issue a setValue call
> which fails when the underlying field is not readable.
>
> Are the multivalued field manipulators supposed to be able to perform 
> such heroic modifications of inputonly fields?
>
> --Brad Vender

Hmmm, that's an intersting one.  But I think its a bug in our 
implementation.  My addChildren is a writeable field.  Set1Value is a 
write service.  So I can't see why it wouldn't be allowed.

Justin, does this jive with your reading of the SAI spec?
--
Alan Hudson

President Yumetech, Inc.                               www.yumetech.com
President Web3D Consortium                             www.web3d.org
206 340 8900
-------------------------------------------------------------------------
for list subscription/unsubscription,
go to http://www.web3d.org/cgi-bin/public_list_signup/lwgate/listsavail.html