quote:

---

Original post by Ecko
one thing I didn't like is that you have to pass hInstance

try out this:
HINSTANCE hInstance = (HINSTANCE)GetModuleHandle(NULL);

---

quote:

---

the second thing is that the peek message and show window and all that could really be automated...

---

quote:

---

...show window should automatically be shown when the window is created.

---

quote:

---

Original post by Anonymous Poster
Second, what about registering class prevoiusly in the winmain? If i wanna do this i have one prob, the class needs one field lpfnWndProc, that points to the mainwndproc, but it doesnot accept a method of a clas, only a plain proc (like the Win32 threads) There is a way to solve this?

---

quote:

---

Original post by Red Ghost
Just curious: were you inspired by www.relisoft.com/win32/generic.html when designing your own encapsulation ?

---

quote:

---

Original post by Anonymous Poster
On the first page with your first example, your window destructor will not get called when it goes out of scope because it doesn't go out of scope at all (the pointer does). You need to explicitly delete it in that case or place your window on the stack so it does go out of scope.

Similarly, your final example has the same memory leak. g_wnd will not get destructed because you are not deleting it anywhere.

---

Window & MainWin = Window( hInstance );  

quote:

---

Original post by another Anonymous Poster
Second, what about registering class prevoiusly in the winmain? If i wanna do this i have one prob, the class needs one field lpfnWndProc, that points to the mainwndproc, but it doesnot accept a method of a clas, only a plain proc (like the Win32 threads) There is a way to solve this?

---

if( !m_Initialized )
  Init();  

quote:

---

Original post by tcpo
In Window::HandleMessages(), IsExit() is used to check the exit status set by OnDestroy(). Because OnDestroy calls PostQuitMessage, I've tried to replace IsExit() is HandleMessage() with "if (msg.message == WM_QUIT)", but then my program fails to stop. Would that be my silly programming mistake? Or have i misunderstood anything here?

---

quote:

---

So it's logical that the enterprising C++ developer would like to wrap all of the above in a nice class...

---

quote:

---

Original post by Anonymous Poster
is it just me, or does this wrapper seem more complicating as if you would just do it the normal way?

---

quote:

---

Original post by Yet Another Anonymous Poster
If you were a real developer you would either use MFC if you must use the Win32 API (horrible idea if you like standard C++, but writing your own wrappers really is not practical) or use someone elses GUI library (like Trolltech's Qt which also has the advantage of being crossplatform).

---

quote:

---

Nice article besides though.

---

throw "Rubbish"; 

quote:

---

Original post by DerekSaw
Isn't that the 1st msg to be sent by Windows is WM_GETMINMAXINFO instead of WM_NCCREATE?

---

quote:

---

One thing to note, whenever exception occur in the same scope of Window(), problem come.
eg. I put a

throw "Rubbish";  

just after the line wnd.Show() ... it got access violation.

---

throw exception( "Rubbish" ); 

throw "Rubbish"; 

#include "window.h"

using namespace Obsidian;

int WINAPI WinMain(HINSTANCE hinst, HINSTANCE, LPSTR cmd, int show)
{
    try
    {
        Window wnd(hinst);
        wnd.Create();
        wnd.ShowWindow(show);

        throw std::runtime_error(std::string("Rubbish"));

        while(wnd.Dispatch())
            ;

        return wnd.GetExitCode();
    }
    catch(std::runtime_error & ex)
    {
        ::MessageBox(NULL, ex.what(), "Exception", MB_OK | MB_TASKMODAL);
    }
    catch(...)
    {
    }
    return 0;
}
 

quote:

---

Original post by DerekSaw
Anyway, how you all have that syntax-highlighted listbox?

---