Hi Robert,
On 5/01/10 9:26 PM, Robert Osfield wrote:
I've done a quick read of you proposal and it sounds good. For
convenience perhaps adding a getIntProperty(), getFloatProperty() etc.
methods might be appropriate, or perhaps one could use the bool
getProperty(const std::string, Property)
Hi Ulrich,
Guten Rutsch ;-)
I've done a quick read of you proposal and it sounds good. For
convenience perhaps adding a getIntProperty(), getFloatProperty() etc.
methods might be appropriate, or perhaps one could use the bool
getProperty(const std::string, Property) interface that I adopted in
Hi all,
FYI, I don't know if it's exactly the same (I admit I didn't read the entire
thread), but we've discussed about an aggregation of components in osg
classes (see Suggestion: Add components in nodes (aggregation) thread).
Sorry I don't have much time going deeper, but the idea seems
Ok, I've read it all through now, and it looks very good. I agree with both
Bryan's and
Robert's suggestions. I look forward to being able to use this soon, it will be
VERY helpful.
--
Chris 'Xenon' Hanson, omo sanza lettere Xenon AlphaPixel.com
PixelSense Landsat processing
On 12/31/2009 4:22 AM, Ulrich Hertlein wrote:
Hi guys,
I have coded up a proposal for a general-purpose property system for
osg::Object and would
like to present it for comments and discussion.
I'd like to take another day or so to digest this, as I'm very interested in
it. Are you
Hi guys,
I have coded up a proposal for a general-purpose property system for
osg::Object and would
like to present it for comments and discussion.
Properties must be derived from osg::Referenced and are stored in a map by name:
class PropertyMap : public Referenced, public
Robert Osfield wrote on Wednesday, December 02, 2009 4:11 AM:
I've done something similar to this in the OSG in the
osg::ArgumnetParser::Parameter class - this one uses a union
internally like the Variant class above, with the twist that it's for
passing in data to be set so it uses a pointer
7 matches
Mail list logo
