|
#1
|
|||
|
|||
Hi
Thanks for telling us that it can be compiled in vs2008, ill get a copy of that this afternoon(if i can find a copy). Ive only got to recompile animpath.dlm and dldraw.dlr (if anyone has compiled any of these can they post them). Everything else works fine. The new interface is amazing. Im finding the inspector to be really useful aswell. The only problem i had, was when debugging i accidently shut down the local/global window and couldnt get it back with out restarting vizard. Maybe it was me being stupid. Thanks TarkaDahl |
#2
|
|||
|
|||
Sorry I forgot to mention that. You definitely need to compile the plugins using Visual Studio 2008.
We're hoping to finalize the new plugin interface before the final release. When that's ready there will be a more complete example of how to interact with your plugin objects from the Python script. The old style plugins will still be compatible though. |
#3
|
|||
|
|||
Quote:
This came out to be rather complicated Am I doing this right? The below code shows the growing exprression (i send the pointers to cout to still if they're still valid or I've made a mistake). Code:
cout << ((VizCustomNodeObj*)custom)->node << endl; cout << osg::dynamic_pointer_cast<osg::Geode>(((VizCustomNodeObj*)custom)->node) << endl; cout << osg::dynamic_pointer_cast<osg::Geode>(((VizCustomNodeObj*)custom)->node)->getDrawableList()[0] << endl; cout << osg::dynamic_pointer_cast<CustomDrawable>(osg::dynamic_pointer_cast<osg::Geode>(((VizCustomNodeObj*)custom)->node)->getDrawableList()[0]) << endl; osg::dynamic_pointer_cast<CustomDrawable>(osg::dynamic_pointer_cast<osg::Geode>(((VizCustomNodeObj*)custom)->node)->getDrawableList()[0])->ToggleAnimate(); Best, Dee |
#4
|
|||
|
|||
Oh, I have another question:
How do I communicate fatal, execution-halting errors to Vizard from my plugin? As there's C code in between, I can't throw exceptions (right?), so how can I make Vizard stop execution from my plugin then (I know I can send info to stdout from the plugin, so I don't need a way to send a message along as well, just the execution halt)? Thanks! Dee |
#5
|
|||
|
|||
Ah, another thing I hope you could add to the documentation:
The plugin is compiled with _SECURE_SCL=0. This means that if you call functions in libraries that also take stl containers, those libraries also have to be compiled with preprocessro definition set. Otherwise, vectro has a different size and you get difficult to trace errors (I just spent a few hours on this)... Best, Dee |
#6
|
|||
|
|||
The debug panes (Call Stack, Locals, Globals) are automatically made visible when debugging starts and hidden when debugging ends. If you accidentally close the pane, then restarting the debugger should bring it back up. We'll add some options in the View menu to allow manually bringing the windows back up, in case this happens.
|
|
|