This is normal behavior for event signals. The default handler can stop further processing by returning true. It's described e.g. at https://developer.gnome.org/gtkmm-tutorial/stable/sec-xeventsignals.html.en https://developer.gnome.org/gtkmm-tutorial/stable/chapter-keyboardevents.html.en You shall set the 'after' parameter to false in the call the connect(). https://developer.gnome.org/glibmm/stable/classGlib_1_1SignalProxy.html#a0bee9dba36374339ab19ec34f288613e
Yes, I know that this can happen and set my handlers now "before" the others. What makes me wonder is that it looks that the default handler has changed behavior. Or had I myself programmed some unlucky side effects? :-) Thanks for your detailed answer/link list! Regards Klaus _______________________________________________ gtkmm-list mailing list gtkmm-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtkmm-list
