https://bugs.documentfoundation.org/show_bug.cgi?id=148258
--- Comment #10 from Vince <vre...@cox.net> --- (In reply to V Stuart Foote from comment #9) > (In reply to Vince from comment #8) > > > > > Perhaps I didn't describe it precisely. With a fresh profile, Alt+a brings > > up the table submenu. Since I don't need to access the table submenu very > > often, I prefer for that keystroke to do something more useful to me: > > execute my MyFavoriteMacro. I customize the keyboard to assign Alt+a to do > > just that. > > For vcl backends other than gtk3 it still does. Only the gtk3/4 > implementation has been affected. > > > > > Alt+<key> combinations should not be used for shortcuts at all. > > > > Where does this come from? The capability was introduced a long time ago, > > after lots of impassioned discussion (see > > https://bz.apache.org/ooo/show_bug.cgi?id=4756). I suspect a lot of people > > are using it, including those who reported bug 146174. > > <Alt>+<key> are still fully customizable, except the behavior difference in > handling the accelerators vs. shortcuts got a major tweak for supporting > gtk3 DE with the work on bug 92630, which now splits the accelerator key > sequence. > > <Alt> is now the gtk3 compliant toggle to show the mnemonics assigned, the > underlined character for the lable. > > So now <alt>, <f> in sequence will open the menu; <alt>+<f> will read the > short-cut if assigned in the customize dialog, except on gtk3/4--check it > out with the vcl 'gen', 'kf5', or on a Windows build. > > If you don't like that gtk3 compliance feature, don't use a gtk3 based DE. The gtk3 compliance feature never presented issues. Nothing broke after bug 92630 was resolved. Bug 146174 surfaced after the commit last October which ironically addressed what appears to be a bug in the way gtk3 processes mnemonics (https://bugs.documentfoundation.org/show_bug.cgi?id=144846#c5). The discussion in this thread seems to be focussed around my proposed changes to vcl/unx/gtk3/gtkframe.cxx. I realize that I need to do something better than bypassing the recently introduced code, so I am going to propose a more constructive patch. -- You are receiving this mail because: You are the assignee for the bug.
