🚀 go-pugleaf

Remy Lebeau (TeamB) wrote:
> <user@domain.invalid> wrote in message
> news:3EDEA93A.1090309@domain.invalid...
> 
> 
>>Doesn't the Handled parameter only tell the VCL
>>whether or not to process the message further?
> 
> 
> Correct.
> 
> 
>>Isn't the actual return value for the
>>WM_SYSCOMMAND indicated in
>>some member of the "tagMSG" struct?
> 
> 
> No.  MSG (tagMSG) is not the same as TMessage, which does have a Result
> member.  Messages processed by the OnMessage event handler can't return a
> result value back for the message.  Which is not a bad thing considering
> that the OnMessage event is for processing messages posted to the main
> message queue, which means they were posted with PostMessage() and thus
> can't return any value anyway.  If you're going to return a value for a
> message, then the message has to be processed within the context of the
> form's Dispatch() or WndProc() methods, which are called by the form's
> underlying window procedure in response to messages sent via SendMessage(),
> not PostMessage().
> 
> 
> Gambit
> 
> 

All right, then, isn't that a likely reason why Mike Collins' code is 
not stopping the screen saver? The Windows docs say to return 0 from the 
WM_SYSCOMMAND message to indicate that it has been handled. I'm thinking 
that just not calling the default window proc is not enough. (Which is 
supported by the fact that it isn't working.)