W3C home > Mailing lists > Public > www-svg@w3.org > November 2005

Re: Animation in SVG 1.1

From: Cameron McCormack <cam-www-svg@aka.mcc.id.au>
Date: Fri, 11 Nov 2005 14:05:55 +1100
To: www-svg@w3.org
Message-ID: <20051111030555.GA18269@port.mcc.id.au>

Chris Lilley:
> It is, very much, supported. We found the restriction both undesirable
> and unenforceable, so we ensured that manipulation of attributes through
> script mid way through an animation was well specified. in fact, it
> needs to be anyway because you can have multiple concurrent animations
> on the same attribute.

Excellent.  Can I ask where this is well specified, though?  I can't see
any relevant text in the Animation chapter.

Here are two specific examples of behaviour I'm unsure about.

Say I had this in my SVG document:

  <circle ...>
    <animate id="a" attributeName="r"
             begin="30s; 1m" dur="10s" from="10" to="20"/>
  </circle>

and the current document time was 35s, and with script I did:

  a.setAttributeNS(null, "begin", "30s");

is the new 30s instance time effectively the same as the previous one,
or should the restart semantics be considered because the list of begin
instance times changed?  What if the timing specifier is actually
different but results in a different instance time, such as

  a.setAttributeNS(null, "begin", "a2.begin");

where the a2 animation began at 30s?

The second example is if I had this in my document:

  <circle ...>
    <animate id="a3" attributeName="r"
             begin="10s" dur="10s" from="10" to="20" restart="never"/>
  </circle>

and at 15s, script did:

  a3.setAttributeNS(null, "begin", "40s");

would the element restart at 40s?

Thanks,

Cameron

-- 
  e-mail : cam (at) mcc.id.au    	icq : 26955922
     web : http://mcc.id.au/	        msn : cam-msn (at) aka.mcc.id.au
  office : +61399055779		     jabber : heycam (at) jabber.org
Received on Friday, 11 November 2005 03:06:15 GMT

This archive was generated by hypermail 2.3.1 : Friday, 8 March 2013 15:54:32 GMT