Hi Mike! osgPython runs against OSG SVN version. I don't know if output parameters was working before in osgIntrospection, I didn't test them! In my last mail, I attached a file to test the bug.
What have you in mind to handle reference types? Greets, Miguel 2007/2/26, Mike Wittman <[EMAIL PROTECTED]>:
Hi Miguel, I've been making changes to osgIntrospection lately and I might be able to help out if you can provide some additional information: - what version of OSG is osgPython running against? 1.2 or the latest SVN? - have you ever observed output parameters working previously? I did some minimal testing before making my changes and I don't think I was able to get output parameters working properly then. I'm currently working on some additional changes to more intelligently handle reference types which hopefully should help out with this. -Mike ------------------------------ *From:* [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] *On Behalf Of *Miguel Escriva *Sent:* Saturday, February 24, 2007 9:07 AM *To:* osg users *Subject:* [osg-users] Bug in osgIntrospection Hi! Some osgPython users reported me a bug in output parameters ( for example osg::Quat::getRotate(...) function). I did a C++ test to check if it was a osgIntrospection bug or a osgPython bug. I think it is a osgIntrospection bug, but I haven't the knowledge to fix this. I attach a C++ test file. Greets, Miguel _______________________________________________ osg-users mailing list osg-users@openscenegraph.net http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
_______________________________________________ osg-users mailing list osg-users@openscenegraph.net http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
