Re: [CPP] Storing data in a compileOp

Date : Mon, 12 Dec 2005 15:37:02 +0100
To : XSI(at)Softimage.COM
From : Guy Rabiller <guy(at)alamaison.fr>
Subject : Re: [CPP] Storing data in a compileOp

> Now you sound like Luc-Eric :-)

Oo! Please, tell me you are kidding! :p

> ../.. Operator to operator connection comes to mind ../..

When I'm asking Alan why he would do that, it's not for me to imply he must not, but just to understand the 'design' of his tool - or his approach - because most of the time there is a better way than to start hacking dll or create odd pipes. ;-)
--
guy rabiller | 3d technical director (at) LaMaison




Felix Gebhardt a écrit :


Now you sound like Luc-Eric :-)

Operator to operator connection comes to mind. The fact that one can't store data with the operator instance to be conveniently grabbed from somewhere else is a major bummer. See Syflex implementation for an example of how much hassle is involved.

Not that I'm greedy and would ask for persistent operator data that is automatically stored with the scene, just a little pointer storage space would do.

F.

Guy Rabiller schrieb:

I meant why would you want to call the function from outside of your Class/Operator ?


---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi





---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi


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.