- From: Dr. Olaf Hoffmann <Dr.O.Hoffmann@gmx.de>
- Date: Wed, 9 Aug 2006 09:53:17 +0200
- To: www-smil@w3.org
Hello, ok, thank you, I think, this is very helpful for my understanding of the begin time list and the end time list. As far as I understand now, the end time list is only related to the content of the end attribute and not to all possible end times of the active duration. This seems to be my misunderstanding and confusion with different ends with different meanings. This is much simpler as I expected ;o) Then it is quite clear, that the Adobe plugin and Opera and me are wrong with the interpretation examples like this. The Adobe plugin, Opera and KSVG1 seem to be wrong even with a simpler example like dur="10s" begin="5s" end="4s" Looks really like some further work is needed to get the correct interpretation common too... Thanks again for your help to understand this in detail... > > No further ends are generated. According to the recommendation in the > section Computing the active duration: > "Otherwise, an end value not equal to indefinite is specified along with > at least one of dur, repeatDur, and repeatCount. Then the PAD is the > minimum of the result from the Intermediate Active Duration Computation > given below and duration between end and the element begin: > > PAD = MIN( Result from Intermediate Active Duration Computation, > end - B)" > .... > > There is a difference between having an "end" attribute on an element > and not having an "end" attribute on an element. If you do not have an > "end" attribute, it is more or less like you describe, but if you *do* > have an "end" attribute, it determines the end. The simple
Received on Wednesday, 9 August 2006 07:50:28 UTC