Re: Why cursor keys are not longer reported in key press events

On 2020-03-28 21:52, Klaus wrote:

This is normal behavior for event signals. The default handler can stop
further processing by returning true. It's described e.g. at

You shall set the 'after' parameter to false in the call the connect().

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!


Almost all default handling of signals is done in gtk, not in gtkmm. If something has changed, the change is probably in gtk. In order to find out what has changed, you need to know which version of gtk you used before, and which version you use now. And also which type of widget you see the change in. Different widgets can of course handle signals differently.

This is a kind of change that can very well happen from one release to the next, at least if the minor version number has changed. (Example: some_pkg 2.14.1: 2 = major, 14 = minor, 1 = micro version number)

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]