Ph_EV_PTR_MOTION_BUTTON Filter Callback in PtWindow widgets

Hi,

I am trying to receive Ph_EV_PTR_MOTION_BUTTON events in my window widgets.
I am able to receive this call back in non-window widgets (PtBasic for
example), but in PtWindow widgets. I am using the same code to initialize
and receive the callback in both PtWindow and PtBasic.

I set up the filter callback with the following event mask:
Ph_EV_PTR_MOTION_BUTTON | Ph_EV_BUT_PRESS | Ph_EV_BUT_RELEASE

This is for all widgets (PtWindow included).

The non PtWindow widgets will get all the events, button presses and motion
with a button pressed. The PtWindow on the other hand will get the button
presses and releases only (no motion events with the button pressed).

Is there something I can do to get this or is this disabled for PtWindows?

Thanks
Kevin

I’m not near the documentation right now, so this is just a guess. My
recollection is that one usually uses a raw widget to get the motion
events. Maybe this ability is built into the raw widget, or maybe
into some ancestor widget. In any case, if the Window widget does
not also decend from this widget, it won’t have this ability.

Thanks for the reply Mashoen,

A PtBasic widget will call an event call back on this event. I’ve tested
this. I don’t have a problem with other widgets, just PtWindow.

I have not created a standalone PtContainer or PtDisjoint to see where the
callbacks stop happening (I tired, but if I recall, these aren’t
instnatiated directly, but require a widget to ‘inherit’ them),

Thanks again,
Kevin


“maschoen” <maschoen@pobox-dot-com.no-spam.invalid> wrote in message
news:eg3nm0$6k0$1@inn.qnx.com

I’m not near the documentation right now, so this is just a guess. My
recollection is that one usually uses a raw widget to get the motion
events. Maybe this ability is built into the raw widget, or maybe
into some ancestor widget. In any case, if the Window widget does
not also decend from this widget, it won’t have this ability.