Jump to content

Recommended Posts

Posted

After i started programming in unmanaged C++ i have realized how incredibly much the .NET framework has done to make programming simple. Im now going to show you how to make a window in a Win32 program.

This tutorial assumes that you have a basic knowledge of C++.

 

Lets start with the headers. You need to include <Windows.h> for the window functions, and thats about it. Then, you need your windows main function and your window procedure. I will take you step by step through them.

 

int       WINAPI   WinMain(HINSTANCE hInstance, HINSTANCE hPrevInstance, LPSTR lpCmdLine, int iCmdShow);
LRESULT   CALLBACK WndProc(HWND hWnd, UINT uMsg, WPARAM wParam, LPARAM lParam);

 

Okay thats the easy part. Now for the hard part.

 

int WINAPI WinMain(HINSTANCE hInstance, HINSTANCE hPrevInstance, LPSTR lpCmdLine, int iCmdShow) {
    WNDCLASS wc;     
    MSG msg;
    BOOL Quit = false;
    HWND hWnd = NULL;

 

We will need these two variables to store our window class, for retrieving messages and to decide when to quit.

 

Next comes the code that sets the info about our window. It sets information such as background color, the window procedure, the icon, the cursor, a menu, and most important; the class name.

 

   wc.style = CS_OWNDC;
    wc.lpfnWndProc = WndProc; //Window procedure
    wc.cbClsExtra = 0; //Extra space (in bytes) for the application
    wc.cbWndExtra = 0; //Extra space (in bytes) for each window
    wc.hInstance = hInstance; //Instance
    wc.hIcon = LoadIcon (NULL, IDI_APPLICATION); //Icon
    wc.hCursor = LoadCursor (NULL, IDC_ARROW); //Cursor
    wc.hbrBackground = CreateSolidBrush(RGB(123, 123, 123)); //Background
    wc.lpszMenuName = NULL; //No menu
    wc.lpszClassName = "MyWindow"; //Class name

 

Then we have to register the class

 

 RegisterClass (&wc);

 

Now we have come far enough to create our window, it has been much more work than Dim form = New Form1 hasn't it?

 

 

 

   hWnd = CreateWindow (
      "MyWindow", "Awesome Window Title",  //MyWindow MUST be the same as the lpszClassName ^^
      WS_OVERLAPPEDWINDOW, //Window style
      0, 0, 600, 300, //x, y, width, height
      NULL, NULL, hInstance, NULL); //parent, menu, app instance, ?? lpvoid ??

 

So we have to show our window:

 

  ShowWindow(hWnd, 5);

 

Now comes our message loop, this catches care of all incoming messages and processes them.

 

  while (!Quit)
    {
        if (PeekMessage (&msg, NULL, 0, 0, PM_REMOVE))
        {
            if (msg.message == WM_QUIT)
            {
                Quit = TRUE;
            }
            else
            {
                TranslateMessage (&msg);
                DispatchMessage (&msg); //An indirect call to the WndProc you defined in wc.lpfnWndProc 
            }
        }
        else
        {
            //Application idle
        }         
    }

 

When your application is idle, it means that it has no messages to process, so it is free to do any task.

There is another way of coding the message loop too, that method waits until it gets a message to process, so your application is never idle (as far as i know). Feel free to use the one you like.

 

 

Code:
    while(!Quit) {
        while(GetMessage(&msg, NULL, 0, 0) > 0)
        {
            if (msg.message == WM_QUIT) { Quit = TRUE; }
            TranslateMessage(&msg);
            DispatchMessage(&msg); //Indirect call to wc.lpfnWndProc
        }
    }

 

Finally, we return the result returned from WndProc (wc.lpfnWndProc). 0 for success, and nonzero for fail.

 

 

    return msg.wParam;
}

 

Finally finished you might think, but no. This was just our main window function. Now we need to create our WndProc function. This handles messages for us.

 

LRESULT CALLBACK WndProc (HWND hWnd, UINT uMsg, WPARAM wParam, LPARAM lParam)
{
    switch (uMsg)
    {

 

hWnd is the window handle.

uMsg is the message id/type.

wParam and lParam is additional information for a message.

We have a switch statement to use the right code on the right message. In this tutorial we will handle WM_CREATE (creation) and WM_CLOSE (closing). We will leave the rest to DefWindowProc.

 

 

    case WM_CREATE:
             MessageBox(hWnd, "An awesome messagebox", "Title", MB_OK);
             return 0;
        
        case WM_CLOSE:
             MessageBox(hWnd, "Closing :(", ":'(", MB_OK);
             PostQuitMessage(0);
             return 0;
        
        default:
             return DefWindowProc(hWnd, uMsg, wParam, lParam);
    }
}

 

 

Now, finally we come to an end. If you managed to understand all this, I'm impressed. If everything was copy/paste, try again

Please leave a replay.

 

  • 2 months later...
  • 5 weeks later...
Guest
This topic is now closed to further replies.


  • Posts

    • GoldRush launches tomorrow! July 18 16:00 GMT+3 Europe / International Register your account in the website, connect wallet and be ready to dominate!
    • 🏰 L2EXALTA LEGACY — Interlude x45 📅 Grand Opening: 31/07/2026 — 21:30 (GMT+3) 🌐 Website: https://l2exalta.org/ 💬 Discord: https://discord.gg/zNTCZD4AcT 📌 Wiki: https://l2exalta.org/en/wiki.html#progression   ⚙️ MAIN INFO Chronicle : Interlude Rates : x45 Adena : x50 Spoil : x1 Drop : x5 Safe Enchant : +3 Files : L2OFF   💰 ECONOMY EX Coin : dynamic market currency, mined from monsters, Raid Bosses and Grand Bosses value fluctuates over time Exalta Vouchers : premium currency used for store, donations and EX Coin exchange Exchange : convert EX Coin into Exalta Vouchers Investment options : choose safer or riskier market strategies with EX Coin   ⚔️ PROGRESSION & GEAR Exalta Armors : signature top-tier gear line Forge System : upgrade weapons, armor and jewels with risk/reward mechanics Raid Boss progression tied to materials and prestige   🤖 AUTOFARM Access : Auto Hunting button, bottom-right UI Duration : controlled via tickets or in-game currency Route Mode : record custom farm routes Support Mode : healer/support builds auto-follow, heal and assist party Smart targeting logic with class-specific behavior (mage/archer/melee/support) Captcha designed not to interrupt legitimate AutoFarm sessions   🧪 BUFFER Exalta Buffer NPC/interface Scheme Buffer : save multiple buff loadouts Class presets for mage, fighter, support, PvP   🛠️ SMART GADGETS / QOL Autoloot filter Drop value tracker Boss timer tools Farm stats tracker Auto-consume system In-game server assistant   🗺️ DUNGEON FINDER / PVE Party matching with roles (Tank / Healer / DPS) Ready-check before teleport Monastery of Silence custom PvE zone Party-based reward structure   🎟️ DAILY PROGRESS / EXALTA PASS Daily and weekly tasks (farm, PvP, boss, check-in) Premium Pass track with extra rewards Monastery Daily Quest Reward boards for claiming progress   🏠 HOUSING & EXPEDITIONS Player residences with service NPCs Exalta Spirit Expeditions to themed territories Rewards vary by territory Owner-only access   🏆 PVP / TOURNAMENT Scheduled Tournament system Ranking points from wins/participation Spectator Mode for watching live matches PvP Statues for top-ranked players Anti-feed protections   🛡️ CLAN CONTENT Clan Civil War battlefield event Clan Dungeon Raid content DPS Meter for contribution tracking Support Credit system Classic siege/clan politics preserved   🏪 AUCTION / SHOPS Auction House with seller fee Black Market Dealer (limited-time special offers) Custom shops and multisells Confirmation prompts on purchases/sales   💳 DONATIONS / VIP Donation rewards linked to Exalta Vouchers VIP tiers with comfort/cosmetic bonuses Premium store Gift/promo codes for events   🎥 STREAMER / COMMUNITY Streamer Panel with visible stream links Viewer rewards system Streamer Points for cosmetics/vouchers In-game voice chat (global/party/clan/alliance/command)   🔒 FAIR PLAY Strong Anti-Bot protection Reward protection tied to valid client state Captcha on suspicious activity Staff investigation tools No bots, packet tools or modified clients allowed   👑 GRANDBOSS SPAWNS Orfen : 1 day + 1h random Core : 1 day + 1h random Queen Ant : 1 day 6h + 1h random Zaken : 2 days 12h + 1h random Baium : 5 days + 1h random Antharas : 8 days + 1h random Valakas : 11 days + 1h random   🏅 OLYMPIAD Runs Thursday, Friday, Saturday Heroes change monthly Balanced and fair matchmaking
    • yup basically another one just in case https://drive.google.com/file/d/1UtccbD9e50x3WEnQBab2PTZnBHwpcGYM/view?usp=sharing LineageWarrior.FMagic (CollideActors = True; > False) LineageWarrior.FOrc (CollideActors = True; > False) LineageWarrior.FShaman (CollideActors = True; > False) LineageWarrior.MDarkElf (CollideActors = True; > False) LineageWarrior.MDwarf (CollideActors = True; > False) LineageWarrior.MElf (CollideActors = True; > False) LineageWarrior.MFighter (CollideActors = True; > False) LineageWarrior.MMagic (CollideActors = True; > False) LineageWarrior.MOrc (CollideActors = True; > False) LineageWarrior.MShaman (CollideActors = True; > False) LineageWarrior.FDwarf (CollideActors = True; > False) LineageWarrior.FElf (CollideActors = True; > False) LineageWarrior.FFighter (CollideActors = True; > False)
    • @l2naylondev Requiring a player to log in just for the sake of logging  seems exploitable. Someone could log in only to claim the reward and immediately leave, or repeatedly change their ip. So i guess  are there are additional protections in place ? such as locking the reward by account, character , and ip. It would also be useful to add a playtime requirement. For example, after logging in, the player would need to remain active for at least x playtime  before getting the reward or other parameters configurable by the xml.  I suggest improving the system before selling it. 
  • Topics

×
×
  • Create New...

Important Information

This community uses essential cookies to function properly. Non-essential cookies and third-party services are used only with your consent. Read our Privacy Policy and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..