> Well, I'm not so sure that your definition of ContentAvailable event follow
> the standard spirit (see 8.2 : "available in an optimal state"). However,
Agreed. I often try to find some useful interpretation, which offends
that "spirit".
> - The stream class inherits from the presentable class and is used to
> synchronise components of the stream multiplex. It is neither a visible
> object nor a group of visibles.
> - The video class inherits from the visible class and doesn't redefine the
> activation behavior.
> Consequently, when I read the preparation of the stream, I see that
> initialyActive components are activated. Following the activation behaviour
> defined at 31.3, step 2, I would say that the video is displayed as soon as
> the stream is prepared, even if not playing.
Hm, good point.
> BTW, I think that the deactivation of the stream object should also specify
> that stream components are deactivated as well. I think that "Stop playing
> all active StreamComponents" is definitely not sufficient to be clear and
> explicit.
Maybe it is meant as stopping the components in the external player
rather than within the engine. Again, that is my interpretation.
Maybe the MTF will find a complete opposite solution, which will give
me the chance to extend my contract for an update of the engine. ;-)
Ciao.
Andreas
-- Andreas Zisowsky | mailto:zisowsky@fokus.gmd.de & zisi@cs.tu-berlin.de GMD FOKUS | http://www.fokus.gmd.de/usr/zisowsky Kaiserin-Augusta-Allee 31 | phone: (+49 30) 3463 7262 fax: -8262 D - 10589 Berlin | PGP: finger -l zisowsky@skylab.fokus.gmd.de or WWW