Re: Clarification for SetCursorShape action
Emmanuel BEUQUE (ebeuque@pratique.fr)
Thu, 3 Jul 1997 11:12:18 +0200
À (At) 12:57 +0900 3/07/97, Wataru KAMEYAMA écrivait (wrote) :
>Hi Andreas,
>
>> I have a request for clarification concerning the "setCursorShape" action.
>> In the description in 11.4 the second part of the "Provisions of use" states
>>
>> "NewCursorShape shall refer to an active CursorShape object." (1)
>>
>> In 3 (Terms and definitions) the definition states
>>
>> "An active object has its RunningStatus set to True." (2)
>>
>> An CursorShape object is always active (see 20.1.1), but its RunningStatus
>> attribute inherited from the Root class is never set to True. Therefore,
>> it is not active.
>>
>> I suggest to change phrase (1) to:
>>
>> "NewCursorShape shall refer to an available CursorShape object." (3)
>>
>> What do you think?
>>
>> I have not checked whether this might also be true for other classes like
>> the Palette and Font classes.
>
>We've concluded that CursorShape, Font and Palette shall be always
>active when they are referenced. Therefore, if you look at the
>semantics of InitiallyActive of them, it clearly says that they are
>always active. By the activation behavior of Group, it guarantees
>that all of them are active and their RunningStatus' are always true
>after activation of Group, because InitiallyActive is always set to
>True.
I agree with Wataru on this but I think that Andreas' suggestion is not
totally useless however.
Since setCursorShape object need an active CursorShape object, and since
activation of items is done after the startup actions of a group, this
implies that you cannot use a setCursorShape action within the startup of a
scene if the cursorShape object is defined in the scene itself.
If it only needs to be available, this would work since object are prepared
before the startup.
Therefore, actions like SetCursorShape currently need to be put in a link
fired by the IsRunning event of the scene object, but I have always found
this constraint boring. That's the kind of constraint that make MHEG-5
difficult to produce and that force you to make roundabout ways in order to
fulfil all the provisions of use. Not a good point for MHEG-5.
Just my own humble opinion.
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