Hi Robert
I think merging the osgText::Font and Font3D implementations would be > the cleanest approach. > I think too ... but ... > > Another, more hacky approach would be to postfix the font file name by > .Text3D or something similar and then have the freetype plugin return > Font3D when it detects this. > This solution is really smart, it not break the scalability of osgText. I don't know which use can be done with a font except 2D or 3D glyph, but this keep the door open to other thing. osgText::Text3D have to ensure that name of font file is ended by .Text3D and font file cache coherence is not delegate to the user. I have try this solution and work fine. I prepare a submission if you prefer the second solution. Or implement the first one otherwise. As you want. David > Robert. > > Robert. > _______________________________________________ > osg-users mailing list > osg-users@lists.openscenegraph.org > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org >
_______________________________________________ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
