wxMac EVT_MOTION

Hi,

I am trying to events for when a drag action is being performed on a control. Under Windows EVT_MOTION whenever the mouse cursor is moved. On Mac however it seems that EVT_MOTION events are not generated when the mouse button is held down. Anyone one else seeing this or no a work around?

dragtest.py (701 Bytes)

The button is probably capturing the mouse in such a way that the events are not getting to wx. I don't know if anything can be done about that.

···

On 12/2/10 8:03 PM, Cody Precord wrote:

Hi,

I am trying to events for when a drag action is being performed on a
control. Under Windows EVT_MOTION whenever the mouse cursor is moved. On
Mac however it seems that EVT_MOTION events are not generated when the
mouse button is held down. Anyone one else seeing this or no a work around?

--
Robin Dunn
Software Craftsman

Hi,

Hi,

I am trying to events for when a drag action is being performed on a
control. Under Windows EVT_MOTION whenever the mouse cursor is moved. On
Mac however it seems that EVT_MOTION events are not generated when the
mouse button is held down. Anyone one else seeing this or no a work
around?

The button is probably capturing the mouse in such a way that the events are
not getting to wx. I don't know if anything can be done about that.

Yes it appears that this is only an issue for the native controls.
Generic and composite controls appear to still generate the event.

Its interesting to note that the LEFT_DOWN event is sent but the
LEFT_UP is never sent either so it definitely seems as if the capture
is being stolen internally by the control. I think I have an idea for
a work around though that I will try out.

Thanks,

Cody

···

On Fri, Dec 3, 2010 at 1:30 PM, Robin Dunn <robin@alldunn.com> wrote:

On 12/2/10 8:03 PM, Cody Precord wrote:

Hi Cody,

Hi,

Hi,

I am trying to events for when a drag action is being performed on a
control. Under Windows EVT_MOTION whenever the mouse cursor is moved. On
Mac however it seems that EVT_MOTION events are not generated when the
mouse button is held down. Anyone one else seeing this or no a work
around?

The button is probably capturing the mouse in such a way that the events are
not getting to wx. I don't know if anything can be done about that.

Yes it appears that this is only an issue for the native controls.
Generic and composite controls appear to still generate the event.

Its interesting to note that the LEFT_DOWN event is sent but the
LEFT_UP is never sent either so it definitely seems as if the capture
is being stolen internally by the control. I think I have an idea for
a work around though that I will try out.

Is this Carbon or Cocoa? When I checked into this last, this issue was fixable when using Cocoa, but not Carbon. (A common finding.... :wink:

Thanks,

Kevin

···

On Dec 3, 2010, at 11:34 AM, Cody Precord wrote:

On Fri, Dec 3, 2010 at 1:30 PM, Robin Dunn <robin@alldunn.com> wrote:

On 12/2/10 8:03 PM, Cody Precord wrote:

Thanks,

Cody

--
To unsubscribe, send email to wxPython-users+unsubscribe@googlegroups.com
or visit http://groups.google.com/group/wxPython-users?hl=en

Hi,

···

On Fri, Dec 3, 2010 at 2:31 PM, Kevin Ollivier <kevin-lists@theolliviers.com> wrote:

Hi Cody,

On Dec 3, 2010, at 11:34 AM, Cody Precord wrote:

Hi,

On Fri, Dec 3, 2010 at 1:30 PM, Robin Dunn <robin@alldunn.com> wrote:

On 12/2/10 8:03 PM, Cody Precord wrote:

Hi,

I am trying to events for when a drag action is being performed on a
control. Under Windows EVT_MOTION whenever the mouse cursor is moved. On
Mac however it seems that EVT_MOTION events are not generated when the
mouse button is held down. Anyone one else seeing this or no a work
around?

The button is probably capturing the mouse in such a way that the events are
not getting to wx. I don't know if anything can be done about that.

Yes it appears that this is only an issue for the native controls.
Generic and composite controls appear to still generate the event.

Its interesting to note that the LEFT_DOWN event is sent but the
LEFT_UP is never sent either so it definitely seems as if the capture
is being stolen internally by the control. I think I have an idea for
a work around though that I will try out.

Is this Carbon or Cocoa? When I checked into this last, this issue was fixable when using Cocoa, but not Carbon. (A common finding.... :wink:

On Carbon (2.8.11), unfortunately haven't been able to get the 2.9
cocoa build to run on my machine yet (crashes on import from missing
symbol)

Cody