🚀 go-pugleaf

Remy Lebeau (TeamB) wrote:
> <user@domain.invalid> wrote in message news:3EDFF4DA.90707@domain.invalid...
> 
> 
>>The Windows docs say to return 0 from the
>>WM_SYSCOMMAND message to indicate
>>that it has been handled.
> 
> 
> In order to do that, the message has to be handled in the WndProc() or
> Dispatch() method instead of an OnMessage event handler.
> 
> However, as previously mentioned, using the OnMessage event does work in
> this case.  It's been tested many times, on many machines.  It works.  Why
> it doesn't for for him specifically, I do not know.
> 
> 
> Gambit
> 
> 
> Gambit
> 
> 

Interesting. I was pretty sure that an application needed to return 0 to 
indicate that it had handled a WM_SYSCOMMAND/SC_SCREENSAVER message, and 
thought that the documentation and some sample screen saver code I have 
supported the idea. If that were true, though, it would imply that this 
message is sent to the application rather than posted, which you assert 
is not the case. I'm willing to leave it a mystery, although it might be 
helpful (to the original poster) if someone were to share their working 
implementation.