IV loader bugs/problems

New Message Reply Date view Thread view Subject view Author view

AnitaKishore (kishore++at++electrogig.com)
Tue, 30 May 1995 13:21:43 -0700

On May 30, 3:13pm, Ralph Seguin wrote:
> Subject: IV loader bugs/problems
> Hi. I have a list of problems that I've found with the
> Performer IV loader. I realize that I may have to fix
> this myself, but I am hoping somebody has already solved it ;)
>
>
> Problem:
>
> 3. What is the best way of having Performer support Engines
> and NodeKits? I saw some mention of having node callback
> stuff. We were planning on developing a bunch of our
> own Engine subclasses also.
>
>
> Anybody fixed these already? What about Engines? Got any
> c++ code for it?
>
> Thanks, Ralph
>
>
>-- End of excerpt from Ralph Seguin

I am facing the same problem regarding engine with performer 1.2. It seems
that this version doesn't directly support engines. But Performer
2.0 will. In the meantime I am trying to modify loadIv routine to take care
of engine subclasses.

I think if I include one more "if..then..else" in callback function
"preNode" of loadIv to take care of SoEngine types, which will attach
a structure containing the engine data to the relevant Performer node,
I should be able to import engine info into Performer. Well, thats my
requirement - to get engine data into performer data base. Off course,
since I may or may not have the engine subclass code to link with,
so I will use the DSO concept.

Anyone with experience/knowledge about this, please comment on the
above method. Will this work?

Thanks

Anita Kishore

New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:51:32 PDT

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.