My question is:
"Can anyone out there point out some good <windows.h>/<windows>(i'm not sure if there's a difference) tutorials?"
I know basically NOTHING about the <windows> library and would appreciate some tutorials that explain EVERY line of code (even if it seems obvious).
Even though I don't know much about the Windows library, I do know about 25% of everything c++. Meaning that I can write functional programs.
Although I'm still missing knowledge on the as of yet unnecessary templates,classes(, and some other stuff that I've gotten along fine without).
On my current project here's some of my current "requirements".
1. Keep the console open while also keeping another window open (for OpenGL).
2. Be able to switch between the two windows for output.
3. Know where the mouse is in the OpenGL window. (Anybody know where to find this?)
4. Get real-time (not using cin.get()) key presses/releases from the keyboard for the OpenGL Window. (again where can I find this?)
Other than that everything's been running smoothly.
I'm using the WXDevC++ compiler on a Windows 7 64 bit.
P.S. I don't have internet @ home so my responses to posts may be slow.
Lamblion I tried your link, and the .zip file there has only .vcpp files not .cpp files.
Dinesh subedi I tried your link and there's lots of code snippets, and hardly any full fledged files.
What I'd really appreciate is a lot of source code files (.cpp only) that have many remarks explaining what is going on in the code.
The file you downloaded contains ".c" files. They are virtually the same as .cpp files. You can either leave them as they are, or rename them to .cpp. Either way, there is full code there, and that is a very good basic tutorial for Windows.
However, if you're just starting, you should type in every line of code yourself. Trust me, you'll abosrb it far better that way.
The part about having a console open for console output at the same time as a GUI window has some tricky parts to it. Post back and ask for further details if interested. However, you'll need to make a bit of progress at the Windows Api to grasp it.