Carsten Neumann wrote:
>       Hello Marcus,
> 
> Carsten Neumann wrote:
>> Marcus Lindblom wrote:
>>> Carsten Neumann wrote:
>>>> hm, looking at the code this warning is printed if an the GLObject with 
>>>> the given osgId does not exist. In other words someone is attempting to 
>>>> validate a GLObject that was destroyed - or are you using 
>>>> validateAllGLObjects() that could be the other source of the error I can 
>>>> think of.
>>> Yep, I'm using that. Should I stop worrying if I get such warnings 
>>> during a call to that function?
>> it is probably harmless in that case; validateAllGLObjects simply runs 
>> over all objects and calls validateGLObject for each, even the ones that 
>> are NULL hence the warning. We can add a test to the loop in 
>> validateAllGLObjects to avoid the warning, since from that function 
>> there is no way to tell if it is a problem or not (only the object that 
>> created or "owned" the GLObject can know if it should still exist).
> 
> validateAllGLObjects now (r1897) skips NULL objects, so you should not 
> see the warnings any more when using it.

Awesome! Thanks!

Cheers,
/Marcus


------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users

Reply via email to