Re: How a non-windowed program can receive WM_DEVICECHANGE from Wi
- From: "Alexander Grigoriev" <alegr@xxxxxxxxxxxxx>
- Date: Wed, 31 May 2006 06:28:49 -0700
hInstance is an instance handle of the main exe or DLL which contains the
WNDPROC. When that DLL is unloaded, all classes registered for its HINSTANCE
are automatically unregistered.
"Amanda Lin" <AmandaLin@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:ADAE70C5-DB74-4604-B71E-F3CDB0F8678F@xxxxxxxxxxxxxxxx
Thank you very much.
I have a question about the "hInstance" that RegisterClass() needs to
create
my own window class.
typedef struct _WNDCLASS {
...
HINSTANCE hInstance;
...
} WNDCLASS, *PWNDCLASS;
MSDN says it's "Handle to the instance that contains the window procedure
for the class". Is it the handle of the application or the thread I
created ?
.
- Follow-Ups:
- Re: How a non-windowed program can receive WM_DEVICECHANGE from Wi
- From: Maxim S. Shatskih
- Re: How a non-windowed program can receive WM_DEVICECHANGE from Wi
- References:
- Re: How a non-windowed program can receive WM_DEVICECHANGE from Wi
- From: Robert Marquardt
- Re: How a non-windowed program can receive WM_DEVICECHANGE from Wi
- From: Robert Marquardt
- Re: How a non-windowed program can receive WM_DEVICECHANGE from Wi
- Prev by Date: Re: How to call function from driver in inline assembler
- Next by Date: Re: Calling devcon.exe from within a win32 service?
- Previous by thread: Re: How a non-windowed program can receive WM_DEVICECHANGE from Wi
- Next by thread: Re: How a non-windowed program can receive WM_DEVICECHANGE from Wi
- Index(es):
Relevant Pages
|