This lesson will cover how to build a basic Windows application. Before we get into actually building a window (which is required for DirectX), we will cover how to create an application and add a simple message box. We will do this by learning each step of a "Hello World!" program.

If this is your first time through this code, note that it is not expected that you remember every line of code we go over here. You may, after some time programming, be able to remember them without reference. But for now, know that if you cannot remember the code in the next four lessons, it does not mean you are stupid. ;)

Following is a code sample of a simple 'Hello World!' demo for a Win32 Console Application.

As you most likely are aware, the function main() is used here to start the application and work with Windows. Simply put, main() is where your program starts, and Windows can feed to your program any parameters you decide might be necessary. Of course, there are specific parameters which can be put in here, but we aren't concerned with these and won't be in any of these tutorials.

A Windows program, however, is different in that it has two functions it uses to work with Windows. One of these is exactly like the Win32 Console's main() function. The other one allows Windows programs to be event-driven. Events are occurrences such as the user clicking the mouse, or pressing a key, or a timer reaching zero. When any of these events occur, Windows records the occurence in a message and places the message in a message queue for the program for which the message is intended, in this case, your game. This second function handles these messages and contains code to run when each occurs. We will cover this second function in the next lesson.

To write our first Windows program, we will need to write the first of these functions, WinMain().

The WinMain() function is the equivalent of the main() function in the Win32 Console. It's where the application starts and where you can do some basic intialization. I usually just put the code for creating a window, for the basic loop, and usually some code for a timer. We'll cover each of these in 'The Basics' lessons. Here is the prototype for the WinMain() function:

Ok, so let's take this function apart:

WINAPI

Before we get into the parameters, let's look at something just before them. Between the int and the WinMain is the word WINAPI. WINAPI is a method of passing parameters which comes from the days of Fortran and Pascal. In short, what it does is reverse the order the parameters are passed. They normally pass from right to left, but with WINAPI, they are passed from left to right. The details on why this is are not really important. Windows simply requires it to be this way.

Now let's take a look at each of the parameters in the function:

HINSTANCE hInstance,

This first parameter is an abbreviation for a "handle to an instance". A handle is a 32-bit integer which identifies something, like an object. An instance is a copy of an application. Due to multitasking and the ability to run multiple copies of a program, Windows needs a way to keep track of which programs are which. It does this by giving each instance of any application a "handle to an instance", or an integer which identifies each application from the others. When your program starts, Windows picks a number and puts it into this parameter.

HINSTANCE hPrevInstance,

Here we have another relic of the past. This second parameter stands for a handle to the previous instance. What this means is, if there are multiple copies of an application open, hPrevInstance will contain the handle of the last instance to be created. Theoretically.

Way back before 32-bit processors came around and before Windows 95, multiple copies of the same application were forced to share the same memory space. This complicated things greatly, and it was of interest to many programmers to keep their applications from running multiple copies of themselves. In order to avoid this, hPrevInstance would give the handle to the previous instance (if any) and return NULL if this was the only one, allowing a programmer to detect any running copies.

However, now that we have 32-bit applications, Windows now provides each application with its own memory space, and hPrevInstance is now obsolete. It only exists for backward compatibility and is equal to NULL in every application, despite the existence of other copies.

There is a method of detecting previous instances of an application, but it is beyond the scope of this tutorial. You can learn this method by looking in the MSDN Library under the WinMain Function.

LPSTR lpCmdLine,

This parameter is a long pointer to a string that contains the command line calling existence to the application. Example: If you had an application called "MyApp.exe" and ran it from the Run command prompt in the Start Menu, you could run it like this "MyApp.exe" or "MyApp.exe RunA" or "MyApp.exe RunB". In either case, lpCmdLine would store the entirety of whatever was entered, allowing the program to check for special parameters.

This is useful in game programming for running special modes such as Safe Mode, Windowed Mode, Software-Rendering Mode, Cheat-Code Mode or whatever you want.

int nCmdShow

This parameter indicates how the window is to appear when created. For instance, this could call for the window being minimized, maximized, or normal, or even open a window with it running in the background. You do not need to use these, but they are available if you so desire. Usually you will not use them in game programming, but they can be useful on occasion. Below are some common values that can come from this parameter:

nCmdShow Values:

All right! Enough with the theory! Let's get some code going and some programs running.

We'll take a break here and write a basic program. Let's start out with, you guessed it, a 'Hello World!' program. Here is the code for the program we'll make, and afterward, we'll take the new commands apart and see what's up.

If you run this program, you'll get something like this:

Hello World in Action

Let's take the new parts of this program apart starting from the top and working our way down.

#include <windows.h>

This is a function that creates the message box you saw in the demo. Here is its prototype:

Now let's quickly go over each of the parameters:

HWND hWnd,

HWND is a handle to a window. As we went over before, handles are integers which identify an object. In this case, we're identifying a window. Simple. Because we have no window made, we put NULL, and Windows knows not to have this message come from any window, but the desktop.

LPCTSTR lptext,

This is a pointer to a 16-bit string that contains the text of the message box. Nothing more to it.

LPCTSTR lpcaption,

This is a pointer to a 16-bit string that contains the text of the title bar, or caption, for the message box. Simple.

UINT utype

This parameter determines what the style of the message box is. Following is a list of commonly used values you can put into this parameter (combined with a logical OR operator for multiple values).

To indicate the buttons displayed in the message box, specify one of the following values:

To display an icon in the message box, specify one of the following values:

In game programming, you normally won't need return values, because error messages (which is what you will use this for 99 percent of the time) only have one direction to go in: quit. However, it is still useful to know. Following is a list of return values, letting you know which button was pressed:

Great! You are now officially a Windows programmer. Yes, we've only covered how to make the simplest of programs, but we'll fix that shortly by writing a program to create a window. Let's get to it!