Fell, maybe you know this about QB64 C/C++ windows...

[Pete]

I've been working with Code:Blocks and generating console apps. I can also generate a Win32 window along with a console. What I'm wondering about QB64 is what type of window does it generate? It doesn't seem like it's a console. It seems more like an API generated window for Windows platforms. Any idea?

Also, I've noticed that in QB64, it generates cursors with LOCATE that can be 1 pixel thin, but in the console apps with Code::Blocks C/C++ exe's, the minimum cursor thickness is more like 15 on a scale of 1 to 100, which are the settings. In other words, I can set the cursor state to "1" but it never seems to get thinner than 15 in the generated console. My guess is it is set that way in the Registry. Anyway, QB64 doesn't have that restriction, which makes me think the windows it generates are not actually console windows; but if not, what?

Oh wait, OpenGL. That's probably rendering the windows. I'll have to see if I can look into that more....

Pete

[FellippeHeitor]

Unless you use $CONSOLE, all output is rendered by OpenGL, indeed.

[Pete]

It is amazing what we get from OpenGL and SDL when it comes to window rendering. When you have to set this stuff up yourself, in Windows API, especially, it's a long and daunting process. Disable quick edit, disable and/or control right clicks, title bar manipulation, resizing, character-wrapping, and even the problem with doing something ti hide the console window if you use C/C++ and generate a separate Win32 graphics window.

My experience with C/C++ and Windows, so far, has shown me that it would be better to learn Windows API programming and forget the console apps, altogether. Even QuickBasic did a better job with window rendering than C/C++. Of course, I'm far from knowing enough about C/C++ to make too many "assumptions" on this subject, but the month of June with me working on a text input app sure has me appreciating the power and ease of QB64. 

Pete