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

    • pone los link para descargarlos por fa   
    • Greetings, everyone. I am sharing a configuration designed for any code editor/console with AI agents. This setup allows for expanded context and highly specific skills depending on your project requirements. It also comes with reusable skills ready for immediate use. Current configuration covers: WEB, L2j server datapacks, and L2j dev (including skills for handling decompiled Java datapacks, etc.). I have left a LINK to the original video on which this specific configuration is based. It also contains brief guides on how to implement new skills. You can simply ask your AI agent to review the guide to get started.   https://github.com/zambo420/Supercharge-your-AI-assistant-for-WEB-and-L2-DATAPACKS-dev.-.git   # 🤖 AI Skills Starter Kit - Forum Quick Start > **Supercharge your AI assistant (Claude, Gemini, Copilot)** ## ⚡ Installation in 2 Minutes   ### 1. Download and copy Copy the `Supercharge-your-AI-assistant-for-WEB-and-L2-DATAPACKS-dev.-/` folder to your project root.   ### 2. Rename and structure ``` your-project/ ├── skills/                      # Rename skills_reutilizables → skills │   ├── skill-creator/ │   ├── react-19/               # Copy the ones you need │   ├── typescript/ │   └── setup.ps1               # Copy from templates/ ├── AGENTS.md                    # Copy from templates/AGENTS.md.template └── src/                         # Your code ```   ### 3. Edit AGENTS.md Customize with your skills:   ```markdown   ## Available Skills | Skill | Description | File | |-------|-------------|------| | `react-19` | React 19 patterns | [SKILL.md](skills/react-19/SKILL.md) |   ## Auto-invoke Skills | Action | Skill | |--------|-------| | Working with React components | `react-19` | ```   ### 4. Sync ```powershell .\skills\setup.ps1 ```   ### 5. Done! Restart your AI assistant and start working.   ---   ## 📦 Included Skills (56 Total) ### Frontend - `react-19` - React 19, hooks, RSC - `typescript` - TypeScript patterns - `tailwind-4` - TailwindCSS v4 - `vite` - Build configuration - `zustand-5` - State management - `nextjs-15` - Next.js 15 - `i18next` - Internationalization - `react-router` - React Router v7 ### Backend - `zod-4` - Validation schemas - `ioredis` - Redis caching - `jwt` - JWT authentication - `django-drf` - Django REST Framework ### Testing & AI - `playwright` - E2E testing - `pytest` - Python testing - `ai-sdk-5` - Vercel AI SDK ### Utilities - `skill-creator` - Create new skills - `java-ant-build` - Apache Ant build system - `jira-epic` - Create Jira epics - `jira-task` - Create Jira tasks ### L2J/Game Server (33 skills) - `gameserver-data` - XMLs, multisells, spawns, NPCs - `gameserver-config` - Server configuration files - `authserver-config` - Login server configuration - `client-files` - Client textures, L2Text, system - `lucera2-core` - L2J core patterns, base classes - `lucera2-handlers` - Admin/user commands, bypass - `lucera2-services` - Community Board, ACP, Buffer - `lucera2-scripts` - Quests, NPCs, bosses, events - `lucera2-network` - Network packets - `lucera2-geodata` - Pathfinding, line of sight - `lucera2-ai` - NPC AI, monster behavior - `lucera2-zones` - Zone scripts, restrictions - `lucera2-achievements` - Achievement system - `lucera2-phantoms` - Fake players (bots) - `lucera2-data` - XML/SQL parsers, holders - `lucera2-authserver` - Login server Java code - `lucera2-olympiad` - Olympiad, heroes, nobles - `lucera2-residences` - Castles, clan halls, siege - `lucera2-skills-effects` - Skill effects, conditions - `lucera2-telegram` - Telegram bot integration - `lucera2-events-pvp` - TvT, GvG, CTF events - `lucera2-seasonal-events` - Holiday events - `lucera2-npc-instances` - Custom NPC types - `lucera2-items-inventory` - Items, inventory - `lucera2-clans-alliances` - Clans, wars - `lucera2-voting-ranking` - Voting rewards - `lucera2-siege-duel` - Siege, duel mechanics - `lucera2-pets-summons` - Pets, servitors - `lucera2-promo-rewards` - Promo codes, daily rewards - `lucera2-item-handlers` - Item handlers - `lucera2-instances-dungeons` - Instance dungeons - `lucera2-minigames` - Lottery, Fishing - `lucera2-autofarm` - AutoFarm bot system - `lucera2-party-matching` - Party finder - `lucera2-cursed-weapons` - Zariche, Akamanah - `lucera2-vip-premium` - VIP/premium accounts - `lucera2-extjar-projects` - Creating .ext.jar projects ---   ## 🎯 The Magic Trick The **Auto-invoke** table is the key:   ```markdown ## Auto-invoke Skills   | Action | Skill | |--------|-------| | Creating React components | `react-19` | | Adding TypeScript types | `typescript` | | Writing E2E tests | `playwright` | ```   **Without this table, AI ignores skills.** With it, they load automatically.   ---   ## 📁 Important Files | File | Purpose | |------|---------| | `AGENTS.md` | Main agent configuration | | `skills/setup.ps1` | Syncs to .claude/.gemini/.github | | `skills/*/SKILL.md` | Each skill definition |   ---   ## 💡 Tips 1. **One place only**: Keep all skills in `skills/` 2. **Auto-invoke**: Without this table, it won't work 3. **setup.ps1**: Run after every change 4. **Restart**: AI needs restart to load changes   ---   ## 🔧 Create Your Own Skill   ```markdown --- name: my-skill description: My skill description ---   ## When to Use - When to use this skill   ## Key Patterns - Important patterns   ## Code Examples \`\`\`typescript // Code example \`\`\` ```   Add to AGENTS.md and run `.\skills\setup.ps1`.   ---   ## 🤝 Compatibility - ✅ Claude Code (Antigravity) - ✅ Gemini CLI - ✅ GitHub Copilot - ✅ Cursor - ✅ Any AI that supports AGENTS.md   ---   ## 📚 More Info See `README.md` on github for complete guide and detailed documentation.    
    • hello guys im searching these days to find something like a patch interface i dont know what it is i logged in many servers i love like those graphics the titles and names are more smooth with bold letters ..i logged in euro-pvp.com but deazel(lucera dev) told me that euro-pvp has multiprotocol with interlude and classic ... and i found a server with name l2gamepower thats only interlude and has same graphics .. can someone explain me or help me how can i have this graphics with namers titles more bold letters and in log in has a name with a patch    https://imgur.com/a/0HzBKWk
    • For the first time in thousands of posts I've read on this forum, I’ve actually found a message that is enriching on both a personal and professional level. I’ll take your advice to heart: I’m going to start creating more and stop overthinking things that get me nowhere. I totally agree about the toxic community; it's a shame. Time to keep working. Thanks a lot for your input.   Exactly, that’s why the Scryde method and their merge system work so well. People don't lose their progress and can still keep rushing new servers. Obviously, gameplay has mutated into something much faster-paced, but obviously, this happens in real life too, everyone is more accelerated and on edge. Thanks to social media and mental conditioning. But, well, it’s something we have to accept. Don't even get me started on gambling and online casinos; that’s a whole other topic regarding all the P2W servers.   Really, amen bro.
  • 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..

AdBlock Extension Detected!

Our website is made possible by displaying online advertisements to our members.

Please disable AdBlock browser extension first, to be able to use our community.

I've Disabled AdBlock