Hi, I just investigated a bug in gtkmm3 (which did not exist with gtkmm2 before) which happens when using Gtk::MenuItem::set_accel_path() to assign a global keyboard accelerator to a menu item. Since gtkmm3 the respective keyboard accelerator action is still triggered, but the accelerator keys were no longer displayed in the menu. I first thought this to be a bug in Gtk(3), so I started the discussion about this issue there: https://mail.gnome.org/archives/gtk-devel-list/2018-February/msg00025.html https://mail.gnome.org/archives/gtk-devel-list/2018-February/msg00027.html https://mail.gnome.org/archives/gtk-devel-list/2018-February/msg00028.html https://mail.gnome.org/archives/gtk-devel-list/2018-February/msg00029.html But meanwhile it rather looks like a bug in gtkmm3 to me. Attached you find a quick hack against gtkmm3 which resolved this bug for me. Like I mentioned in the last post on the gtk list, I have no idea why that acceleration label was created explicitly in the gtkmm "MenuItem" class there. Was it still there for purpose or was it just some legacy code? Note that (in gtk3 at least) a GtkAccelerationLabel is automatically always created as child widget by GtkMenuItem even if no acceleration keys are used at all for the menu item. CU Christian
Attachment:
gtkmm3-accel-path.patch
Description: Text Data