I uploaded a patch for this bug to the bug tracker:
https://bugzilla.gnome.org/show_bug.cgi?id=791174
Since I filed this report on the "Quartz" driver component, and since I have
the impression that the Quartz driver is not really maintained right now,
maybe somebody else might review
On Montag, 20. November 2017 08:04:20 CET you wrote:
> >> Since this issue only seems to happen on Mac, and since it worked
> >> flawlessly on
> >> Mac before, and since I see the Quartz implementation hasn't really
> >> changed
> >> (significantly) in the last couple years, was there some kind of
On Sat, Nov 18, 2017 at 3:44 PM, Christian Schoenebeck
wrote:
> On Freitag, 17. November 2017 00:51:25 CET Christian Schoenebeck wrote:
>> What I found out so far is that whenever this problem occurs, both of the
>> following two checks in function
On Sat, Nov 18, 2017 at 3:34 PM, wrote:
> On Sat, Nov 18, 2017 at 6:45 AM Christian Schoenebeck <
> schoeneb...@linuxsampler.org> wrote:
>
>> On Freitag, 17. November 2017 00:51:25 CET Christian Schoenebeck wrote:
>> > What I found out so far is that whenever this
On Sat, Nov 18, 2017 at 6:45 AM Christian Schoenebeck <
schoeneb...@linuxsampler.org> wrote:
> On Freitag, 17. November 2017 00:51:25 CET Christian Schoenebeck wrote:
> > What I found out so far is that whenever this problem occurs, both of the
> > following two checks in function
On Freitag, 17. November 2017 00:51:25 CET Christian Schoenebeck wrote:
> What I found out so far is that whenever this problem occurs, both of the
> following two checks in function gtk_menu_motion_notify() (gtkmenu.c) return
> false and the function is thus aborted at this point:
>
>
Hi!
I am currently investigating a menu handling bug of Gtk 3.22.26 on Mac (Quartz
implementation). It happens quite often that Gtk 3 menus on Mac stop
processing any mouse events. So when that happens, i.e. menu items are no more
highlighted when moving the mouse pointer over them, nor do the