Re: [CPP] CRef reference persistence

Date : Fri, 16 Dec 2005 09:51:26 +1100
To : XSI(at)Softimage.COM
From : Aloys Baillet <aloys.baillet(at)gmail.com>
Subject : Re: [CPP] CRef reference persistence
OK, but how XSI would delete an object without telling anyone about it?
That would be quite mean of him :-)
And what kind of 'information' is refered by the CRef? UserDataBlob, Kinematics...?
I would say that the SDK provides an interface to the object, and if the object is not here, the interface becomes invalid...
I would vote 'no' to your question.
I would be curious to see what's the real behavior, though!

Aloys

On 16/12/05, Guy Rabiller < guy(at)alamaison.fr> wrote:

Coucou Aloys :-)

> ../.. Application().ExecuteCommand("DeleteObj", oArgs, oRtn); ../..

Yeah that's why I said:
"../.. ( by XSI, not the user ) ../.."

If I delete it myself I would understand the CRef becomes invalid :-)

But imagine that this object was refering ( by 'him' only ) to some
'information', and I got a CRef on that 'information' elsewhere.
If that object got deleted, the 'information' needed by the object would
be logicaly deleted - as nobody need it anymore - but now that I got a
CRef on it, it must be 'kept alive' right ? Or 'reference counted' ?.

I mean, I'm pretty sure I can answer 'yes' to my own question but there
might be subtle cases ( or problems ? ) where it is not the case. I just
wanted to know if it is guaraned or not.

Oh well, I will see it soon enough if there are problems, I guess. ;-)

Cheers
--
guy rabiller | 3d technical director (at) LaMaison





--
Aloys Baillet - XSI Technical Director
Character Dpt - Animal Logic
--

Search the XSI List archives here or use the advanced search form to search across mailing lists. Searching help is available.
This site supposedly brought to you by Benjamin Grosser and the Imaging Technology Group.