Hi Wang Rui, I only want to note that you can utilize the mechanism of QT to not to define the moc keywords like emit, signal, or slot. See at the bottom of this link to the documentation[1]. I had the same problem time ago, and I resolved it with a define clause, something like #define QT_NO_EMIT.
Cheers. [1]http://doc.trolltech.com/4.6/signalsandslots.html 2010/7/20 Wang Rui <[email protected]> > Hi Robert, > > The osgParticle::Emitter class has an important virtual method emit(), > which emits numbers of particles every frame. Unfortunately, the Qt > GUI does define a same macro which is used for its signal and slot > machanism. That means osgParticle and Qt can hardly be merged in one > source file, for there will always be plenty of compile errors. > > The attached files should solve this problem. I've changed all the > emit() to emitParticles() to avoid naming confilct, but also declared > the emit() method if it is not used before, to try keeping > back-compatibility for osgParticle users. > > The following few weeks I'll go full steam ahead different particle > effects, to satisfy my clients. I'd like to contribute some of my > placers and operators to the 'centuries-old' osgParticle library then. > Hope they can be finished and accepted before 3.0 so I can introduce > some more about particles in my book. :) > > Cheers, > > Wang Rui > > _______________________________________________ > osg-submissions mailing list > [email protected] > > http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org > > -- Jordi Torres Fabra gvSIG 3D blog http://gvsig3d.blogspot.com Instituto de Automática e Informática Industrial http://www.ai2.upv.es
_______________________________________________ osg-submissions mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
