i’m developing a network monitor here at work, and its interface is made with opengl.
the application uses a FSM to manage itself, and while initializing it must show various steps, with onscreen messages.
opengl is being initialized correctly in a framework i wrote, and the FSM is invoked only when opengl is online (i can render things, set states and so on)
i start to invoke the FSM: it begins to startup by creating a thread where it initializes network connections, alarm management, in particular a text class (global) and various opengl states/params such as projection and modelview matrix, culling, depth testing…
the main FSM, just after the call to CreateThread() enters in a render cycle, where it waits from messages from the startup function. once a message is ready, it displays it via the text class.
the application starts, and begins to initialize, but seems like the startup thread don’t consider opengl initializations.
the opengl initializations and text class are working properly, because i tested them in a rendering loop, so the problem is not there.
among the other things, in the startup code i move the origin from the window center to the lower left corner with a gluOrtho2D() call, but the message still appear in the center.
are there some considerations when multithreading with opengl?
thanks for any help
[This message has been edited by dmy (edited 02-26-2000).]