Hi Jason and Christophe,

 

Operator overloading is a known deficiency.  But it's unlikely to be resolved 
in an automated fashion in the near future due to extensive changes necessary 
in osgIntrospection.

 

The solution for now is ad-hoc support on a per-type basis, added to the 
generator.  If you know how to patch the generated files to support the 
operators you're using, then it's only a small step to add that same 
information to the generator configuration so that it is added to the generated 
code automatically in the future.  Just modify GeneratorConfiguration.cpp, send 
a patch, and I can integrate it into osgDotNet SVN.

 

On the general question of osgDotNet use, I'm actually only using the wrappers 
intermittently at this point due to some changes in project direction.  But I 
still intend to support osgDotNet releases on top of stable OSG releases in the 
future.

                                                                                
                                             

 

Mike Wittman

[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> 

___________________________________________________

Seismic Micro-Technology, Inc.

8584 Katy Freeway, Suite 400 / Houston, Texas 77024

Tel.  +1 (713) 464-6188

Fax. +1 (713) 464-6440

Web:  www.seismicmicro.com <blocked::blocked::http://www.seismicmicro.com> 

___________________________________________________

CONTACT US TODAY for more information.

 

________________________________

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jason Beverage
Sent: Tuesday, September 18, 2007 10:49 AM
To: OpenSceneGraph Users
Subject: Re: [osg-users] Use of osgDotNet Wrappers

 

Hi Christophe,

Its good to hear you're using the new wrappers.  I believe the operator 
overloading was something that Mike was taking a look at.

Thanks!

Jason

On 9/18/07, Christophe Medard <[EMAIL PROTECTED]> wrote:

We are, for a use from C# projects.

The fact is that some accessor functions are lacking of some important classes 
(example Osg.NodeCallback.operator()()).

The solution adopted for instance - which isn't satisfying for will raise 
problem when the osg API evolves - is to patch manually the header and source 
files generated by the osgDotNet Generator from the osgwrapper_*.dll ...

 

Regards

-- 
Christophe Médard
Société OKTAL (http://www.oktal.fr)
2 impasse Boudeville
31100 Toulouse (France)
Tél. : (+33) 5 62 11 50 10
Fax : (+33) 5 62 11 50 29

        

        ----- Original Message ----- 

        From: Jason Beverage <mailto:[EMAIL PROTECTED]>  

        To: osg users <mailto:[email protected]>  

        Sent: Tuesday, September 18, 2007 5:27 PM

        Subject: [osg-users] Use of osgDotNet Wrappers

         

        Hi everyone,
        
        I'm just curious to see how many people are currently using or are 
interested in using the new osgDotNet wrappers with their applications?  My 
company is currently using our own custom .NET wrappers for OSG but we're 
interested in transitioning to Mike's wrappers and I wanted to get a feel for 
the number of people in the OSG community that would be using the new osgDotNet 
wrappers. 
        
        Thanks!
        
        Jason
        
        

        
________________________________


        _______________________________________________
        osg-users mailing list
        [email protected]
        
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


_______________________________________________
osg-users mailing list
[email protected] 
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org 

 

_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Reply via email to