Re: gdkwindow - gdk_window_get_pointer and gdk_window_at_pointer

[Kent Sandvik <sandvik gmail com>]

On Tue, 31 Aug 2004 16:57:07 -0400, Owen Taylor <otaylor redhat com> wrote:
> On Tue, 2004-08-31 at 16:30, Kent Sandvik wrote:
> > Hi, why is gdk_window_get_pointer() and gdk_window_at_pointer()
> > ignoring the passed in win_x and win_y mouse pointer values? Instead
> > they are using temp variables, and based on the compiler the temp
> > variables  might have somewhat OK values (as the code base is not
> > initializing temp stack variables to either correct or incorrect
> > values) that then later will cause no focus and no hi-light happening
> > for the mouse-over event generation (that relies on a valid GtkWindow
> > returned based on the mouse pointer values)?
> >
> > In case the APIs have changed, could the passed in win_x and win_y
> > values be removed so that there are no misunderstandings?
> 
> I think basically you just need to reread those functions a few more
> times. Remember that win_x/win_y are *out* parameters. Places to store
> the retrieved values.

Oh silly me,  I was looking at the  GDK DirectFB calls that called
gdk_window_at_pointer with NULL, NULL for the passed win_x, win_y
values, and didn't look deeper down at the function that that the x,y
values are synthesized out. Sorry. --Kent


-- 
Something, Anything!