Hi Thiago,
Thiago Bastos wrote:
>
> Well, whatever that means... ;-)
> Still a long way to go learning the new architecture. When will you prepare
> a presentation about OpenSG 2.0 and release the slides for download? :-D
We're doing a course at VR 09, but it's a very, very short one. We'll
have some quick'n'dirty notes for it, but they will cover the main parts.
> (I thought about asking for documentation, but I guess that would be asking
> too much ;-))
Yeah, well, that's always a bit of an issue... ;)
> Doh, I wish every problem could be solved as easily as this one.
> Indeed that did the trick. I was clicking the X button on the GLUT window,
> and if I press "ESC" it doesn't crash.
> As simple as it was, I would never have thought of it. Thanks.
We should probably go back to an atexit handler then, to avoid that problem.
> BTW it didn't go completely without warnings, it still complained about the
> following:
>
> WARNING: SharePtrGraphOp::setIncludes: Unrecognized type [Material].
>> WARNING: SharePtrGraphOp::setIncludes: Unrecognized type [StateChunk].
Those I don't understand. Why do those show up?
>> WARNING: ThreadManager::shutdown: thread [OSGAppThread|02D97828] is still
>> alive ([0]).
>> WARNING: ThreadManager::shutdown: lock [OSG::Log::_pLogLock|02F8AAF8] is
>> still alive
>> WARNING: ThreadManager::shutdown: lock [OSGTMStoreLock|02713AE0] is still
>> alive
Can we just remove those, Gerrit? Or at least relegate them to INFO or
DEBUG? Given that they're normal, I don't see why they're WARNINGs.
Yours
Dirk
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users
