Hi Richard, On 2/12/07, Schmidt, Richard, SDGE1 <[EMAIL PROTECTED]> wrote:
The current CVS version doesn't fix these bugs.
OK. To recap: * When using "Microsoft Sans Serif" the whitespaces don't get rendered. Other letters appear correctly. I don't know if this is a freetype bug... Could you provide an example of this? Spaces do not render with osgText, this is how its intened, white space is not something you render. Is it simply that the spaces are the wrong width? Gordon Tomlinson made some changes to work around broken MS fonts, these are now checked in, perhaps the white space issue is another borken part of the fonts that we don't yet have a work around for. Perhaps use a decent font would be the alternative. * Somehow the boundingbox/origin computation of osgText is off. As a workaround we place it at 0,0,0 and than transform the geode at the desired position. Any ideas, why it doesn't compute the bounding box correctly? I can't not answer this one, as as far as I'm aware the compute of the bounding box is correct. You'll need to provide a concrete example to illustrate what you think is a problem. * With it's custom drawimplementation osgText doesn't seem to support overwriting statesets properly. It would be great if it supports statessets like other osg nodes do. osgText::Text has to manage StateSet's in a special way as it has to deal with the textures associated with the glyphs, note that their might be mulitple textures that it has to swap in as required. Robert. _______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
