Re: Clarification for ObjectReferenceVariabl

Emmanuel BEUQUE (ebeuque@pratique.fr)
Tue, 10 Mar 1998 19:42:37 +0100

À (At) 17:37 +0100 10/03/98, Andreas Kraft écrivait (wrote) :
>Emmanuel,
>
>On Tue, 10 Mar 1998, Emmanuel BEUQUE wrote:
>> BTW, you cannot reference a variable in a scene from the application.
>> Within application, you can only reference scene as external
>> references.
>
>Why? I would guess you can have a shared link which access a variable in
>a Scene object. You just have to write the fully qualified ObjRef of the
>variable. Of course, it might be that the according scene isn't loaded
>so an elementary action which addresses this variable doesn't fire (because
>there is no valid target).

I based my opinion on reading 5.3, 50.1, and 51.

I'm perhaps wrong and it perhaps needs some clarifications but here is my
humble opinion :

51 specify neither how to make a reference to a scene ingredient from
within application nor to another scene ingredient from within a scene.
This assumption is confirmed by 50.1. 5.3 also said that Application
objects are available to scenes. It is not said in 5.4 that referencing an
object in another scene is not allowed but we could assume that.

To me, it seems difficult for an engine to build a reference to an object
that is not prepared. That's the aim of so many provisions of use of MHEG
actions.

I assume that the problem is the same when giving a value to an
ObjectRefVar, either by OrigValue or by SetVariable. I know that 25 doesn't
specify that the new variable value shall reference an available object but
I always prefered to consider this.

I'm interested in having the opinion of other MUG members.

Is it allowed in all known engines of MUG members that GenericObjectRef can
reference any ingredients, including some in another scene ?
What if the ingredient do not exist ?
And if some think that it is not allowed, what do they do when a shared
ObjectRefVar reference an ingredient in a scene and the scene is destroyed ?

These points could perhaps be clarified if it is not clear for everyone else.

BR,
Emmanuel

__________________________________________________________________
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