Spawn a thread that creates a window with a handle. Problem is you still
need a message pump to dispatch said message when it comes in, so a console
app would need some pump thread and the DLL would need one or need to be in
a windowed app. Really you should figure out how to have it as a regular
app with a pump.
I'm kinda new to doing windows & mobile development, so this may be
obvious
to most, but I'm having trouble finding a decent solution.
I need to get some notifications that require a window handle to be passed
in for the request but I'm trying to do this in a dll or from a command
line
program that doesn't have a window associated with it. What is the best
way
to satisfy the request's (in my current case the SHChangeNotifyRegister()
call) need to have a window handle to return the notification to?
Focus and Messages ... Because of how the message pump is setup, the program takes 99% of the cpu cycles and slows everything down. ... Someone gave me the suggestion to put a WaitMessagecall after cdx_DoFrameand that works closest to what I need, it only takes up processing power when I'm using the app but if the window is not in focus, it doesn't receive any messages, only when I refocus it do all the messages process and draw, I need that to happen even if the window isn't in focus. ... after the cdx_doFrame on the server app, it will not process any messages until I refocus the window or move my mouse across it. ... I setup the app to send a custom message when network data was received to notify me) but the message box only popped up when I refocused the window. ... (microsoft.public.win32.programmer.messaging)
Re: Cant Move Overlapped Window to Front ...message pump (or is it busy doing something, ... But when I attempt to activate my window,... or are you perhaps drawing from elsewhere in the ... >> doesn't let any other app to regain ... (microsoft.public.vc.mfc)
Re: Application interaction with the shell ... A dialog gets its own message pump - separate from the one you normally create over in WinMain. ... Sending it WM_CLOSE simply exits that pump, which will return to the caller that opened the dialog. ... Sending WM_CLOSE to the apps pump won't affect the dialog, in fact I presume it will just queue it up and once the dialog closes, it will get dispatched to nowhere since the dialog's handle no longer exists. ... I've written an app which uses a dialog template to create its main window.... (microsoft.public.windowsce.app.development)
Re: Thread Deadlock ... How can an app update... > does not get out of the event handler until the dialog is closed. ... Every window has a function that gets called when a message needs to be ... This function is called from a Message Pump.... (microsoft.public.vc.mfc)
Re: Regular DLL & message pump: No messages recived ... > I'm trying to create a regular MFC DLL to use as an interface in an Win32 ... The DLL contains one window derived from CDialog and the main app... > the message pump into the ServerUIUpdate function, ... (microsoft.public.vc.mfc)
