> OK. Who will do it? Are you attending the Stockholm meeting?
No. Someone from Fokus?
> I think we have found another related problem.
> The internal behaviours for Activation and Deactivation of the Audio class
> are missing. The problem is that it is never actually activated because it
> inherits from Ingredient and Presentable, but not from Visible as the other
> stream components (Video and RTGraphics). Because neither Ingredient nor
> Presentable set the RunningStatus to true and generate the IsRunning event,
> an Audio object is never really activated.
> I therefore propose to add the following to 38.3 (Internal Behaviours):
> 1. Execute the Activation behaviour as defined in the base class.
> 2. Set the RunningStatus to True and generate an IsRunning event.
> Note: The actual playing of an Audio object is started during the
> Activation behaviour of the Stream object the Audio object is a
> component of.
> 1. If the RunningStatus attribute of the object is False, ignore the
> behaviour, otherwise:
> 2. Stop playing the Audio.
> 3. Execute the Deactivation behaviour as defined in the base class.
I think you are right. However, the deactivation behavior is to be
left as it it, because the 2nd point is explained in Stream class and
Audio class and the 1st point is already defined in the base class.
** Wataru KAMEYAMA, Dr., ASCII Laboratories Inc., JAPAN
** TEL: +81 3 5351 9711
** FAX: +81 3 5351 9750
** email@example.com ($B55;3!!>D!w%"%9%-!<L$Mh8&5f=j(B in KANJI)