On 24/04/07, Roode, Eric <[EMAIL PROTECTED]> wrote:
For what it's worth, I have always been unclear on what the Win32::GUI doco means by "the event is not passed to the default event processor". Any clarification, anywhere, would be useful.
OK. The default handling of an event depends on the control. For example, consider a left mouse click (_MouseDown). For a Window, the default processing does nothing, so being able to stop it is, o be honest, not very useful. But, for a button, the default processing of a left mouse down (performed by the control itself), is to re-draw the button in the depressed state, and capture the mouse, waiting for a mouse up event to occur. In this case intercepting the _MouseDown event, before the button sees it and preventing it being passed to it's 'default handler' it would have the effect of stopping the user clicking the button. In general it's always advisable to allow messages to be passed on to their default handler's, and only prevent that if there are known side-effects that you want to stop. Regards, Rob.
