Hi Neil,
On Wed, May 27, 2009 at 9:40 AM, neil.hug...@tesco.net wrote:
I hope you're over your cold/flu now?
On the mend thanks, still not 100%, but able to work just fine.
I'm looking at the PluginStrData work , and wondered whether you think the
setPluginStrData and getPluginStrData should be made case insensitive? I was
thinking to force the 'set' parameters through the osgDB::convertToLowerCase
function. It would make checking for specific option string settings a little
cleaner, and more robust.
FYI, I renamed the method is s/getPluginStringData(). As to whether
to make it case insensitive on setting, I would generally avoid
enforcing this, what you set is what you get. For instance if you
want to encode a human readable phrase then for sure you would want to
keep case. For options it's a bit different, but it's on reading the
options you can decide whether you want to treat it as case
insensitive.
Robert.
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
