2. Mouse events seem to be screwed up. After clicking on my
OpenGL area widget, other widgets will not receive
enter-notify-event until I click again outside the widget, making
buttons and other widgets not work. Is there a way to fix this?
same here.
I hacked around this one, probably break
On Mon, 2010-02-15 at 14:33 -0500, Shawn Bakhtiar wrote:
>
>
> FYI ---
>
> The same thing happens on the OS X version using the Native GTK (NON X
> Windows). No mater where the widget. It always takes up the entire
> windows, and does not respond to mouse input.
>
> Could it be that the issue i
> Subject: Re: gtk+-2.18, win32, and OpenGL
> From: al...@redhat.com
> To: t.ev...@aranz.com
> Date: Mon, 15 Feb 2010 10:21:01 +0100
> CC: gtk-devel-list@gnome.org
>
> On Mon, 2010-02-15 at 12:07 +1300, Tim Evans wrote:
> > Previous with GTK+ 2.14 I had some custom
On Mon, 2010-02-15 at 12:07 +1300, Tim Evans wrote:
> Previous with GTK+ 2.14 I had some custom code that would let me draw
> with OpenGL into a widget under win32. After updating GTK+ 2.18 this
> code doesn't work properly any more, it turns the entire toplevel
> window
> into an OpenGL area i
On 2010-02-15 12:07, Tim Evans wrote:
Mouse events seem to be screwed up. After clicking on my OpenGL area
widget, other widgets will not receive enter-notify-event until I click
again outside the widget, making buttons and other widgets not work. Is
there a way to fix this?
I found I can work
