What should I do?
Posted in Uncategorized on March 28th, 2009This is a WTF moment which happened to me whilst trying to save a Power Point presentation from GDC. I was a little confused on what action to take.

This is a WTF moment which happened to me whilst trying to save a Power Point presentation from GDC. I was a little confused on what action to take.


Well not quite.
Yesterday saw the release of the new OpenGL 3.1 specification, actually they released two. One which has the fixed function removed and the other which exposes an extension string GL_ARB_compatibility, which if supported by your driverĀ indicates that the driver has backward support. Nvidia were fast out of the block announcing their Beta OpenGL 3.1 driver which supports the extension string, as to whether AMD/ATI will support it is yet to be seen. So if you are not using shaders now is as good a time as any to learn, speaking of which Khronos released the new specification to GLSL last month. For more details see the specifications or the Khronos press release.
DirectX XNA also released/announced a couple of goodies yesterday including the March DirectX SDK and XNA 3.1 (is this version number a coincidence? ) .
Update:
ATI have confirmed that they will be supporting the GL_ARB_compatibility extension.
I do not know at what point my Win32 window creation code changed but I have been trying to track a bug which until just now I was unable to find the source. I sub-class the window to allow the message procedure function to be a class member and therefore attaching the this pointer in CreateWindowEx. I had the correct flags set for the style so that the window had a title bar, yet the title was not being shown and the only way I could hack around it was to send a WM_SETTEXT to the window. The problem was due to the handling of the WM_NCCREATE message.The msdn documents state:
If an application processes this message, it should return TRUE to continue creation of the window. If the application returns FALSE, the CreateWindow or CreateWindowEx function will return a NULL handle.
What if fails to state is that the message needs to be passed to the default window procedure or a window title is not shown. I do not know if this is the only side effect which happens but it was the only noticeable one I could find.