I've wondered about this too... More specifically, I was wondering if osgInit
and osgExit could be called multiple times in a row, as long as there is one
exit for each init:
osgInit(...)
osgInit(...)
...
osgExit()
osgExit()
The code didn't look like it could handle that, but it would really come in
handy... (Ideally, it would be nice if there was no such thing as osgInit and
osgExit, but it doesn't seem like that's feasible :)
Chad
Allen Bierbaum wrote:
Is it reasonable and safe to repetitively call osgInit() then osgExit()
in a single application?
The code I am working on is not an OpenSG application, but is a plugin
routine for another application that allows it to create an opensg graph
and then save it out.
Right now I am looking at code that would be something like this:
void exportGraph()
{
osgInit(0,NULL);
.... do the export ....
osgExit();
}
Is this a "good" way to do this from the OpenSG standpoint?
-Allen
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users
