Hi Marco,
Thanks for the file. I've done the test and don't see any stateset's shared
so I can reproduce the issue you are seeing so its a good first step.
As for what piece of code should be fixed, I think it's much a design
choice. A fundamental question is: what is the postcondition of
Hi Robert,
So yes, UNSPECIFIED help solve the problem of deciding what data variance an
StateAttribute should have, if the user has explicitly set STATIC or DYNAMIC
then this is a formal decision made by the user and its inappropriate to
override this with automatic codes that try to work
Hi Marco,
On Thu, Apr 3, 2008 at 5:08 PM, Marco Jez [EMAIL PROTECTED] wrote:
If you agree, I can patch the LWO reader so that it sets state
attributes' variance to STATIC. This would solve my issue entirely (as I'm
only loading LWO files). Code based on older versions of OSG won't be
if (itr-second.first-getDataVariance()==UNSPECIFIED
(itr-second.first-getUpdateCallback() ||
itr-second.first-getEventCallback()))
{
itr-second.first-setDataVariance(DYNAMIC);
}
else// - ADDED this block
{
4 matches
Mail list logo
