W3C home > Mailing lists > Public > www-smil@w3.org > April to June 2003

events vs syncbases, what gets cleared during reset

From: Annie Chang <anniec@adobe.com>
Date: Fri, 9 May 2003 16:38:17 -0700
Message-ID: <017001c31684$112bc080$b6422099@ADOBEMWA1EHEVN>
To: <www-smil@w3.org>
Hello,

I have a question about what gets cleared during a reset. Under "resetting element state", #1 says that times associated with event-values, repeat-values, accesskey-values or added via DOM method call are cleared. Am I correct in thinking that event values are times that cannot be previously computed, such as media ends and user clicks? If so, does this mean that all resolved syncbase instances stay in the instance times lists for the lifetime of the program, even when the element gets reset? If so, how does the element computing its next interval figure out which ones not to use?

What is the desired behavior in the following example:
<par>
 <par id="p" begin="5s" dur="100s" >
 <img id="b" begin="a.begin+1s" end="9s"/>
 </par>
 <img id="a" repeatCount="5" begin="0s" end="3s"/>
</par>

What will happen at time 5s?
Will b begin at 1s into the media at time 5s since the computed time of a.begin+1s first happened at 4s? Or will it wait until time = 7s in to begin?

How about this one:
<par>
 <par id="p" begin="0s" dur="2s" repeatCount = "5">
 <img id="b" begin="a.begin+1s"/>
 </par>
 <img id="a" begin="0s" dur="3s" repeatCount="5"/>
</par>

What times does b start?
At 1s, it should start because it depends on a. What about at 2s, when it gets reset? If only events are cleared out of instance timelists and not syncbases, won't b always begin immediately when its parent container begins, since it is dependent on a, which will have begun long ago? This does not seem like it would be the desired behavior.

Thanks,
Annie
Received on Friday, 9 May 2003 19:34:01 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:53:28 GMT