Hi,
On Wed, 2011-02-09 at 17:50 +0800, Gerrit Voß wrote:
> Hi,
>
> On Tue, 2011-02-01 at 09:50 -0600, Patrick Hartling wrote:
> > On Feb 1, 2011, at 1:09 AM, Gerrit Voß wrote:
> >
> > >
> > > Something else I would like to integrate the python bindings back into
> > > the cmake system.
> > >
> > > Currently I plan to have them live of a pyopensg checkout and pull
> > > things during the cmake run as needed (as we do with the support stuff).
> > > I don't want to have a diverging duplicate of the original pyopensg
> > > project.
> > >
> > > The only part where this seems to break (from early tests) seem to be
> > > the gen_bindings.py script. So there I would have to have some kind of
> > > duplication of which I have figure out how to keep it in sync with the
> > > main pyopensg developments.
> >
> > There is some manual post-processing that has to be done after running
> > gen_bindings.py. I think there are three cases where Py++ generates code
> > contrary to what it is supposed to do. The other case has to do with
> > Py++ not currently understanding that OSG::GLUTWindowBase and
> > OSG::PassiveWindowBase
> > have OSG::Window as a base class. I haven't figured out the cause for that
> > problem.
>
> ok, I'm not that far yet, my biggest issue so far are the pure virtual
> function from FieldContainer, for example createAspectCopy or the
> shallowCopy variants. They seem to get thrown into a wrapper rather
> randomly. Right now I find them in ShaderProcVariableBase
>
> struct ShaderProcVariableBase_wrapper : OSG::ShaderProcVariableBase,
> bp::wrapper< OSG::ShaderProcVariableBase > {
>
> ::OSG::FieldContainer * createAspectCopy( ::OSG::FieldContainer
> const * arg0 ) const {
> return
> OSG::FieldContainer::createAspectCopy( boost::python::ptr(arg0) );
> }
>
> };
>
> Looking at ShaderValueVariableBase, which has the same structure
> (abstract intermediate class, derived from ShaderVariable) I don't
> find these included.
>
> Something is strange, I can't really point to a difference in these
> classes. Any hint what might cause this is really welcome.
arrg, few more minutes thinking, it seems to be an order problem. If
I take them out (ignore = true,
set_virtuality(pd.VIRTUALITY_TYPES.NOT_VIRTUAL) immediately after
creating the module_builder the problem is gone ;).
kind regards
gerrit
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Opensg-core mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-core
