New Window style ? How ?

[marten]

I've been working on the OpenGL code for some days now and still have problems with the correct initialization of Smalltalk windows and rendering contexts etc.

I created a new subclass of CwDrawingArea. The idea was, that the content of the OpenGL output should be rendered into instances of this subclass. As I understand each widget has its own window (nder Windows) and one must register a new window class with the following styles: CS_HREDRAW | CS_VREDRAW | CD_OWNDC. How can that be done under VASmalltalk ?

When opening the window the window itselfs should have some options like CLIPCHILDREN and CLIPSIBLINGS ... whats the correct way here to do it right. I've found all of the stuff somewhere in the images - but I do not get the overall picture ?!

Actually I managed to get the rendering output into my subclass of CwDrawingArea (but actually only some part of it) - but I do not get all events needed to redraw the widget correctly - and whenever I start the image the first time my code runs it fails completely ...

Any idea or help possible ?

Marten

[tc]

Hello,

I have not done specific OpenGL work but working with windows widgets, it seems, one would create a subclass in the CwWidget hierarchy and do the same in the OSWidget hierarchy or in your case, have an OpenGL hierarchy that follows the same pattern as the OSWidget hierarchy.

The OSWidget/OpenGL hierarchy is where the styles would be set, clipping is handled, clipping of siblings, events come in, etc. To me, the pattern of how a CwWidget communicates with an OSWidget would be the same for a CwWidget/OpenGL hierarchy.

--tc

[marten]

Hello,

I have not done specific OpenGL work but working with windows widgets, it seems, one would create a subclass in the CwWidget hierarchy and do the same in the OSWidget hierarchy or in your case, have an OpenGL hierarchy that follows the same pattern as the OSWidget hierarchy.

The OSWidget/OpenGL hierarchy is where the styles would be set, clipping is handled, clipping of siblings, events come in, etc. To me, the pattern of how a CwWidget communicates with an OSWidget would be the same for a CwWidget/OpenGL hierarchy.

--tc

I've gone in this direction. I created a new subclass of CwDrawingArea and also a corresponding subclass of OSComposite (CwDrawingArea corresponds to OSComposite) and connected them each other. I created a new classmethod "windowClass" and "initializeWindowProc".