Re: OnStartUp actions

Emmanuel BEUQUE (ebeuque@pratique.fr)
Tue, 4 Nov 1997 10:02:37 +0100

À (At) 21:54 +0100 3/11/97, Andreas Kraft écrivait (wrote) :
>answering an older e-mail from you:
>
>On Thu, 30 Oct 1997, Emmanuel BEUQUE wrote:
>
>> Another solution would be that a new version of MHEG-5 specify that
>> variables only need to be available in order to be used, or that a variable
>> is always active. Any thought whether this could be a problem ?
>
>This would be an exception from all the other objects which have some kind
>of life cycle. I don't think that this is a good idea.

I agree if we statuated that a variable is always active. But what about
the fact that actions would only require the variable to be available.
In fact, MHEG objects have 2 levels in their life cycle (available, and
then active). These 2 levels are necessary for presentables. It allows the
engine to be aware of some objects (when available) that are not presented
to the user.
But I think this second level is totally useless for variables. It is only
there to make the standard more consistent but I really don't see the need
of 2 levels for variables such as Font, Palette or CursorShape which all,
BTW, must be initially active.

In fact, as Run and Stop are defined in the presentable class, I would have
find more logical to define the active state in the presentable class (with
the exception of links that must have 2 states...).

>> 2. Suppose you want to define some action-slots for a ListGroup that should
>> be empty (or at least has less items than cells). You are obliged to define
>> dummy items in the ListGroup in order to be able to attach some action
>> slots. Then the OnStartup is a good place for "DelItem" with reference to
>> all the dummy items you don't want to activate.
>
>This is something you can do using a scene-IsRunning-link, isn't it?

Yes but it could also cause some flickering effect (and anyway cause
useless actions) if you do it in a scene IsRunning link instead of the
OnStartup.

By the activation of the listGroup at the end of the activation of the
scene, all the dummy items you were obliged to define will also be
activated (but you may want them to remain stopped). So you would be
obliged to also stop them in the isRunning link and this
activation-deactivation would cause a flickering effect except if you have
chosen invisible visibles (hotspot or null size visibles).

That why I think it is definitely better to delete the useless items in the
OnStartup rather than in the scene IsRunning link.

Regards,

__________________________________________________________________
Emmanuel BEUQUE mailto:ebeuque@pratique.fr
MediaServ tel: +33 (0) 2 99 64 35 64
Multimedia consultant & developer fax: +33 (0) 2 99 64 36 65