There is no reason why I could possible explain this... But there's a chance that I just fixed the blitz runtime-window problem. And totally by accident.
The reason why this seems crazy is because WinDowse claims that the WS_CLIPSIBLINGS style already was applied to the runtime window. Furthermore, the problem that it fixed was the runtime window messing with its children - not its siblings.
Um... That was nonsense. I'm good at nonsense.
Basically, setting that style on the Blitz Runtime window appears to make it possible to parent another totally operating win32 window to it.
BB_3D_View = Create3DScene(VisWin,0,0,width-255,height-75,0) style = apiGetWindowLong(BB_3D_View,GWL_STYLE) style = style Or WS_CLIPSIBLINGS ;Why this makes it work, I will never know. apiSetWindowLong(BB_3D_View,GWL_STYLE,style)
The reason why this seems crazy is because WinDowse claims that the WS_CLIPSIBLINGS style already was applied to the runtime window. Furthermore, the problem that it fixed was the runtime window messing with its children - not its siblings.
Um... That was nonsense. I'm good at nonsense.
Basically, setting that style on the Blitz Runtime window appears to make it possible to parent another totally operating win32 window to it.