<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>
    </div>
    <blockquote type="cite"
cite="mid:CAKdk67so8n3eQVVS-FA8yJUYL0ZGwVRCxwe-96PGzQq2Bitt9g@mail.gmail.com">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <blockquote class="gmail_quote" style="margin:0px 0px 0px
              0.8ex;border-left:1px solid
              rgb(204,204,204);padding-left:1ex"><br>
              This is a very reasonable suggestion. As you point out,
              there would be<br>
              no way to get an empty key field except when keyValue was
              also empty.<br>
            </blockquote>
            <div><br>
            </div>
            <div>The only situation I can vaguely imagine when empty key
              and keyValue fields would be useful is an initial state
              which does not want to be immediately changed to a
              functional, fully populated interpolator. But this would
              be likely a misuse since activation like this should be
              done more explicitly.<br>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    Yes, there should be an 'active' field that turns an interpolator
    on/off. Or better, bundle the TimeSensor functionality needed for
    interpolation with the Interpolator. This would include the regular
    controls for on/off/pause/resume/etc.<br>
    <br>
    <br>
    <blockquote type="cite"
cite="mid:CAKdk67so8n3eQVVS-FA8yJUYL0ZGwVRCxwe-96PGzQq2Bitt9g@mail.gmail.com">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <blockquote class="gmail_quote" style="margin:0px 0px 0px
              0.8ex;border-left:1px solid
              rgb(204,204,204);padding-left:1ex">
              ...<br>
              I haven't looked, but I suspect A-Frame uses TWEEN to do
              the<br>
              interpolations....<br>
              <br>
            </blockquote>
            <div><br>
            </div>
            <div>Yes, A-Frame uses TWEEN. The proposed default key value
              would correspond to the default TWEEN behavior. I had
              raised an issue with Tween here to discuss keyed
              animation:</div>
            <div><a
                href="https://github.com/tweenjs/tween.js/issues/352"
                moz-do-not-send="true">https://github.com/tweenjs/tween.js/issues/352</a><br>
            </div>
            <div><br>
            </div>
            <div>As discussed there it turns out that by using custom
              (piecewise) interpolation or custom easing it is already
              possible to do key frame animation with Tween. This is
              what I do for the A-Frame keyframes component. So I do not
              think there will be changes to Tween although the
              maintainer expressed some interest.</div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    <br>
    I should review that issue. From what I read of the docs and code,
    it would be difficult to get non-evenly spaced keys. The developer
    would need to calculate the position along the path for evenly
    spaced points to make that work. Yes, it could be done with varying
    durations and chaining, but it would start to get real messy with
    easing and non-[piece-wise]-linear paths.<br>
    <br>
    <br>
    <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>