[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: motion notify event messages.



Looking at the C source for the gtk widgets I've noticed that all the widgets that don't work correctly in Lazarus (x coord's relative to the parents form instead of itself) don't assign a motion_notify event in the class_init function.  Does this mean that the motion events are not really handled by a button and are really being sent from the form?

Is the form getting the motion-notify and passing it on to the button because the button has grabbed the pointer (left mouse button was clicked on the button)?

Shane


>>> Havoc Pennington <hp@redhat.com> 10/29/01 04:31PM >>>

"Shane Miller" <SMiller1@stvgb.org> writes:
> That's what I thought.  Here's what I did.  I created the button and
> wrote down the pointer returned (136791384).  Then I created the
> ENTRY control and wrote down the pointer (136977848).
> 
> When I held the left-mouse button down on each one and moved the
> mouse, I observed the GTKWidget value passed into the callback,
> along with the GDKEventMotion's X and Y coordinates.  The widget
> value was always the value that was returned from the creation of
> the control (the pointer value 136791384 or 136977848). However, the
> X and Y values were either relative to the control (the entry
> control) or relative to the Button's parent (the gtkwindow).
> 
> Any thoughts?  

Make a small test case we can look at, we'll take a look.
Hard to speculate on what might be wrong without seeing code.

Havoc
_______________________________________________
gtk-app-devel-list mailing list
gtk-app-devel-list@gnome.org 
http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]