[x3d-public] Turning on and off simultaneous animations individually

[John Carlson]

But probably the issue could have been I didn’t use a DEF in the in the
initializer.

John
On Tue, Feb 4, 2025 at 4:45 PM John Carlson <yottzumm at gmail.com> wrote:

> Michalis, here’s a different approach I took, and hit a brick wall with
> all browsers.
>
> I did provide a simple initializer, which didn’t appear to change anything.
>
> John
> ---------- Forwarded message ---------
> From: John Carlson <yottzumm at gmail.com>
> Date: Tue, Feb 4, 2025 at 12:56 AM
> Subject: Re: Turning on and off simultaneous animations individually
> To: Andreas Plesch <andreasplesch at gmail.com>, Michalis Kamburelis <
> michalis.kambi at gmail.com>, Holger Seelig <holger.seelig at yahoo.de>, GPU
> Group <gpugroup at gmail.com>
> CC: X3D Graphics public mailing list <x3d-public at web3d.org>, Joe D
> Williams <joedwil at earthlink.net>
>
>
> Indeed, moving the TimeSensor  USE to a fieldValue makes Castle report
> this:
>
> castle-model-converter: Warning: X3D: Route destination node name "clock"
> not found
> castle-model-converter: Warning: X3D: Route destination node name "clock"
> not found
> castle-model-converter: Warning: X3D: Route destination node name "clock"
> not found
>
>
> Seems like I've made a full circle.  Now I can't get anything to work.
>
> So option B) sounds really good, and I'll just recommend Sunrize, or do
> scripting.
>
> What I can try to do is provide an initializer value to clock in
> ProtoInterface.
>
> see attachment.
>
> John
>
> On Mon, Feb 3, 2025 at 12:11 AM John Carlson <yottzumm at gmail.com> wrote:
>
>> I have no problems with your thinking Andreas.  My only questions are 1)
>> Why am I chosen to find these corner cases? 2)  Can Castle Model Viewer
>> support ECMAScript soon, perhaps in an Electron or better WebView? 3) It
>> would seem like ProtoInterface field accessType="outputOnly" needs to be
>> treated specially.
>>
>> Primarily, I am concerned that A) alone will not solve 3) above and B)
>> may be required.  Castle Model Viewer already has A), which is helpful, but
>> I don't have a workaround yet.
>>
>> On Sun, Feb 2, 2025 at 10:40 PM Andreas Plesch <andreasplesch at gmail.com>
>> wrote:
>>
>>> Apologies in advance if the following comes across as a bit of
>>> rigid thinking for a corner case but unfortunately there is now an example.
>>> A larger standard question is how to correctly process a fieldValue
>>> statement with a default value for the value attribute.
>>> The XML schema for fieldValue says that the default value for the value
>>> attribute is "", the empty string. Relying on that default is rarely,
>>> perhaps never, a useful use of fieldValue but is allowed.
>>>
>>> Scenario A)
>>> In the case the field for which such a fieldValue is given is of type
>>> SFTime, this would strictly mean that the value is invalid since the "" is
>>> not an encoding of a floating point number and does not pass the regex
>>> test. Therefore processing could become undefined and should be halted.
>>>
>>> Scenario B)
>>> Another, perhaps less strict but more useful interpretation is that the
>>> empty string for SFTime signals the lack of a value and that therefore a
>>> default value for the SFTime field should be adopted. This default could be
>>> an initial -1 as the Tooltips suggest, and would likely be overwritten.
>>>
>>> A) is stricter and follows the rules more literally. B) is perhaps
>>> more often what authors intend but may need some clarification in the
>>> specification.
>>>
>>> This applies only to the XML encoding.
>>>
>>> I think the XML encoding for fieldValue should require one of: an
>>> existing value attribute, or at least one child node (as a XFNode value).
>>> Not sure if the XML schema could handle that.
>>>
>>> Would you prefer A) or B) ?
>>>
>>> Personally A) with some error messages but some X3D browsers accept B).
>>>
>>> Thanks, Andreas
>>>
>>>
>>> On Sun, Feb 2, 2025 at 4:58 PM Andreas Plesch <andreasplesch at gmail.com>
>>> wrote:
>>>
>>>> I think x3dom, reasonably, expects a value for the fieldValue nodes:
>>>>
>>>> For example:
>>>>
>>>> <fieldValue name="startTime" />
>>>>
>>>> and others.
>>>>
>>>> On Sun, Feb 2, 2025 at 5:42 AM John Carlson <yottzumm at gmail.com> wrote:
>>>>
>>>>> Andreas, Joe,
>>>>>
>>>>> Reset Button, Reset_Clock added.
>>>>>
>>>>> See attached zip for details, or visit link;
>>>>>
>>>>>
>>>>> https://create3000.github.io/x_ite/playground/?url=https://raw.githubusercontent.com/coderextreme/ci2had/refs/heads/main/resources/CleanedYouClocks.x3d
>>>>>
>>>>> For some reason, this link doesn't show the live scene?
>>>>>
>>>>>
>>>>> https://andreasplesch.github.io/Library/Viewer/index.html?url=https://raw.githubusercontent.com/coderextreme/ci2had/refs/heads/main/resources/CleanedYouClocks.x3d
>>>>>
>>>>> Puzzled, haven't researched it yet.  Looks good in Sunrize and X_ITE,
>>>>> will try FreeWRL next.
>>>>>
>>>>> John
>>>>>
>>>>>>
>>>>
>>>> --
>>>> Andreas Plesch
>>>> Waltham, MA 02453
>>>>
>>>
>>>
>>> --
>>> Andreas Plesch
>>> Waltham, MA 02453
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20250204/7842ae46/attachment.html>