<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Andreas,<br>
<br>
This is a very reasonable suggestion. As you point out, there
would be no way to get an empty key field except when keyValue was
also empty. <br>
<br>
I haven't looked, but I suspect A-Frame uses TWEEN to do the
interpolations. TWEEN automatically provides evenly spaced keys
when given multiple keyValues. I was planning on working on an
upgrade for that sometime this fall. Please let me know if you are
going to make modifications to TWEEN.<br>
<br>
Leonard Daly<br>
<br>
<br>
<br>
</div>
<blockquote type="cite"
cite="mid:CAKdk67s0FqrNC3PvZatsb-9d7RKxZO1dbS5gvqEz5xaRVb3B2g@mail.gmail.com">
<div dir="auto">
<div dir="auto">The default key field value is [ ], empty.</div>
<div dir="auto"><br>
</div>
<a
href="http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/interp.html#X3DInterpolatorNode"
moz-do-not-send="true">http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/interp.html#X3DInterpolatorNode</a>
<div dir="auto"><br>
</div>
<div dir="auto">recognizes the validity of an empty key field,
which then means no events are generated and no interpolation
happens.</div>
<div dir="auto"><br>
</div>
<div dir="auto">Is that behavior useful for any situation ? A
serious question, perhaps for prototypes somehow ?</div>
<div dir="auto"><br>
</div>
<div dir="auto">I am developing an Aframe equivalent to
interpolation nodes (<a
href="https://github.com/andreasplesch/aframe-keyframes-component"
moz-do-not-send="true">https://github.com/andreasplesch/aframe-keyframes-component</a>)
and weigh other default key values.</div>
<div dir="auto"><br>
</div>
<div dir="auto">Specifically, I am leaning towards a default
which provides constant intervals for keyValues. If there are
5 keyValues, the default keys would be [0,0.25,0,5,0.75,1].
This is what most commonly may be the expected behavior from
an interpolator. Given n keyValues, default keys are [0/(n-1),
1/(n-1) .., (n-1)/(n-1)].</div>
<div dir="auto"><br>
</div>
<div dir="auto">The benefits of such a default are least
surprise, and more concise scenes.</div>
<div dir="auto"><br>
</div>
<div dir="auto">The drawback is backwards incompatibility
although I have not seen a scene which uses the default key
field value.</div>
<div dir="auto"><br>
</div>
<div dir="auto">My goal is to raise a better informed
specification comment as I feel there may be more to consider.</div>
<div dir="auto"><br>
</div>
<div dir="auto">Any comments are very welcome,</div>
<div dir="auto"><br>
</div>
<div dir="auto">Andreas</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
x3d-public mailing list
<a class="moz-txt-link-abbreviated" href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a>
<a class="moz-txt-link-freetext" href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a>
</pre>
</blockquote>
<p><br>
</p>
<div class="moz-signature">-- <br>
<font class="tahoma,arial,helvetica san serif" color="#333366">
<font size="+1"><b>Leonard Daly</b></font><br>
3D Systems & Cloud Consultant<br>
LA ACM SIGGRAPH Chair<br>
President, Daly Realism - <i>Creating the Future</i>
</font></div>
</body>
</html>