Re: [wx-dev] Click events
David Barnard
Sure, it makes a good substitute, which is probably why the question
is asked so rarely. But a) it doesn't propagate, being a mouse event
not a command event, and b) it fires at times when a click event isn't
expected, such as at the end of a drag action.
On Sun, Jul 27, 2008 at 8:39 PM, Vadim Zeitlin <va...@wxwidgets.org> wrote:
> On Sun, 27 Jul 2008 20:36:30 +0100 David Barnard <da...@didactylos.net> wrote:
>
> DB> What am I missing?
>
> EVT_LEFT_UP?
> VZ
>
> _______________________________________________
> wx-dev mailing list
> wx-...@lists.wxwidgets.org
> http://lists.wxwidgets.org/mailman/listinfo/wx-dev
>
Vadim Zeitlin
DB> As I tried to explain, EVT_LEFT_UP is not equivalent to a click.
Well, it definitely is equivalent to a click from Win32 API point of view
(because this is what it is). Maybe I'm irremediably corrupted by Microsoft
influence but using it seems like a perfectly sensible way to handle mouse
events to me.
DB> Sure, it makes a good substitute, which is probably why the question
DB> is asked so rarely. But a) it doesn't propagate, being a mouse event
DB> not a command event,
You can make it propagate by using ResumePropagation() method although I
can't say I recommend it.
DB> and b) it fires at times when a click event isn't
DB> expected, such as at the end of a drag action.
If the mouse is being dragged, it must be captured by some window. And if
you capture the mouse you should be ready to handle this event for it too.
Regards,
VZ