Hi Mario,
Mario Lüttich wrote:
> Hi Dirk
>
> I use now the Daily Build and i have new problems. If I start my program
> the Error is:
>
> "Managed Debugging Assistant 'LoaderLock' has detected a problem in
> 'D:\\Projects\Debug\test.exe'.
> Additional Information: Attempting managed execution inside OS Loader
> lock. Do not attempt to run managed code inside a DllMain or image
> initialization function since doing so can cause the application to hang."
>
> I have a DLL that needs OpenSG to Display something. (you can say I have
> a wrapper for SimpleSceneManager). Inside a singleton I init opensg but
> that isn't the problem. The problem occurs if i insert the OpenSG headers.
>
> No I found the Problem does not occur if I use opensg in debug mode.
> (OSGBaseD.lib OSGSystemD.lib OSGWindowWin32D.lib) I think if my dll is
> initialized then the opensg is initialized and opensg sets a thread lock
> and the init function is never left.
>
> I hoppe you see what i mean
Well, I'm not a Windows expert, so honestly I have no clue what that
message is supposed to mean.
One thing you can try is to not use the Windows GL Window but the
PassiveWindow instead. That way you can use whatever initialization is
necessary for OpenGL inside the framework you're using and avoid
interference with OpenSG internals.
So if you can get an OpenGL app running the way you need it, you can get
OpenSG running the same way.
Hope it helps
Dirk
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users
