GNOME Bugzilla – Bug 590656
use-underline should be default true for buttons
Last modified: 2009-08-17 07:41:02 UTC
Please describe the problem: Several apps have recently broken in that they should an underscore instead of an underline mnemonic/accelerator. The Win32 API has this by default for buttons as far as I can tell, but their character is '&' (ampersand). Since using '_' in a button is rare, we might as well enable use-underline by default. I'm not sure if this affects all buttons. Some other reports mentioned it only affected buttons with icons, but that's not been my experience. Steps to reproduce: 1. Start up Users and Groups administration applet. 2. Observe that the Unlock button looks like _Unlock instead of Unlock with an underlined `U'. Actual results: Expected results: Does this happen every time? Other information: Related launchpad report: https://bugs.launchpad.net/gst/+bug/404767
And yes it happens every time with the same applications on the same buttons. But for some reason only on some buttons. It may only be the ones that are dynamically created rather than with glade. I don't know though. That's just an example. I have certainly edited a glade file to fix the issue in some apps.
there were bugs related to _ handling in both gtk and glade. With recent versions, this should all just work.
Matthias: Cool. Do you know what revision distributions should sync in order to get the updates, or what commits fixed the problem?
git log might tell you.
Matthias: Could you give more explanations? The bug we face [1] is that the default seems to have changed so that now mnemonics are disabled in buttons. The fix is pretty straightforward, but I'd like to be sure I need to enable mnemonics by hand before committing that fix to the gnome-system-tools. The GTK+ log history did not help... Thanks!
The default has not changed. A bug was fixed that led to underlines being interpreted in some situations despite use-underline being FALSE.
OK, I see. The default has always been false, and we've relied on that bug. So the right thing is changing that property.