[frameworks-kconfig] [Bug 482149] F10 as menu shortcut steals it from applications
https://bugs.kde.org/show_bug.cgi?id=482149 --- Comment #10 from Felix Ernst --- Yes, Shift+F10 could work. This way there would still be some keyboard-only way to go to the menu. It's also a common enough change from the typical shortcuts that a user might be able to guess it. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 482149] F10 as menu shortcut steals it from applications
https://bugs.kde.org/show_bug.cgi?id=482149 --- Comment #9 from Nate Graham --- Shift+F10 in Konsole would make sense to me, and match how other common shortcuts are handled in terminal apps to avoid conflicting with CLI software. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 482149] F10 as menu shortcut steals it from applications
https://bugs.kde.org/show_bug.cgi?id=482149 --- Comment #8 from Ivan --- > Of course any change we ever make (even if it is during a major transition > from Qt 5 to Qt 6 like this) will go against previously expected behaviour. > I don't really see though in what way what you are saying disagrees with me. > I do agree with your point that it is unwanted when a terminal program's F10 > shortcut doesn't work because it was stolen by Konsole. But this doesn't > change the argument I made which was: "When a completely blind person sits > in front of Konsole and tries to go to the menu F10 is their only option > AFAIK. Take that away and they can't even open the help menu AFAIK." I disagree that conservative approach is not a way to go. Terminal is very special application and it should be excluded from a "normal" behaviour. IMHO F10 to open a menu is a stupid idea in the first place in the same way as F11 for full screen etc. It may work well in a browser, but not in all applications. And when it comes to terminal - it's not just an app, it's a container for running apps. I don't think that terminal should be aware what keys are used in a terminal app and to decide when to open the menu or to pass. I have lots of scripts I created that utilise all F keys. And I always loved Konsole. Suddenly I'm in a big trouble. Not to mention popular apps like mc, htop etc. IMHO getting rid of this "feature" is a way to go, or at least adding something like shift+F10, like they did for copy-paste (ctrl+shift+c). I wouldn't be surprised if someone wants to use ctrl+c in terminal for copy :) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 482149] F10 as menu shortcut steals it from applications
https://bugs.kde.org/show_bug.cgi?id=482149 --- Comment #7 from Felix Ernst --- (In reply to András Manţia from comment #5) > This bug is even more annoying than I thought: the shortcut keeps resetting > itself That would be annoying but it would be considered unrelated to this bug. (In reply to Ivan from comment #6) > (In reply to Felix Ernst from comment #4) > > I am not sure "being conservative" works here. When a completely blind > > person sits in front of Konsole and tries to go to the menu F10 is their > > only option AFAIK. Take that away and they can't even open the help menu > > AFAIK. > > > > That's why I suggested that Konsole should only give up control of the F10 > > key when the current terminal application uses it. This way the general > > accessibility of Konsole doesn't have to suffer just because some terminal > > applications also want to use F10. > > I disagree. F10 is often used in terminal applications. People are used to > Ctrl+C and Ctrl+V and other common shortcuts, but that's not how it works in > Konsole. The same should be applied to F10 and F11. > > I'm pretty much blind and when I'm using terminal apps like I'm used to > instead of getting F10 action from my application I'm getting some useless > menu. > > In my opinion this is serious bug Of course any change we ever make (even if it is during a major transition from Qt 5 to Qt 6 like this) will go against previously expected behaviour. I don't really see though in what way what you are saying disagrees with me. I do agree with your point that it is unwanted when a terminal program's F10 shortcut doesn't work because it was stolen by Konsole. But this doesn't change the argument I made which was: "When a completely blind person sits in front of Konsole and tries to go to the menu F10 is their only option AFAIK. Take that away and they can't even open the help menu AFAIK." -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 482149] F10 as menu shortcut steals it from applications
https://bugs.kde.org/show_bug.cgi?id=482149 Ivan changed: What|Removed |Added CC||knezivan...@gmail.com --- Comment #6 from Ivan --- (In reply to Felix Ernst from comment #4) > I am not sure "being conservative" works here. When a completely blind > person sits in front of Konsole and tries to go to the menu F10 is their > only option AFAIK. Take that away and they can't even open the help menu > AFAIK. > > That's why I suggested that Konsole should only give up control of the F10 > key when the current terminal application uses it. This way the general > accessibility of Konsole doesn't have to suffer just because some terminal > applications also want to use F10. I disagree. F10 is often used in terminal applications. People are used to Ctrl+C and Ctrl+V and other common shortcuts, but that's not how it works in Konsole. The same should be applied to F10 and F11. I'm pretty much blind and when I'm using terminal apps like I'm used to instead of getting F10 action from my application I'm getting some useless menu. In my opinion this is serious bug -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 482149] F10 as menu shortcut steals it from applications
https://bugs.kde.org/show_bug.cgi?id=482149 --- Comment #5 from András Manţia --- This bug is even more annoying than I thought: the shortcut keeps resetting itself to F10 from time to time (I don't know yet when it happens) despite changing it to "None". Configure Keyboard Shortucts Dialog also shown the Open Menu entry twice. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 482149] F10 as menu shortcut steals it from applications
https://bugs.kde.org/show_bug.cgi?id=482149 --- Comment #4 from Felix Ernst --- I am not sure "being conservative" works here. When a completely blind person sits in front of Konsole and tries to go to the menu F10 is their only option AFAIK. Take that away and they can't even open the help menu AFAIK. That's why I suggested that Konsole should only give up control of the F10 key when the current terminal application uses it. This way the general accessibility of Konsole doesn't have to suffer just because some terminal applications also want to use F10. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 482149] F10 as menu shortcut steals it from applications
https://bugs.kde.org/show_bug.cgi?id=482149 --- Comment #3 from András Manţia --- In my opinion Konsole is special and should be conservative in what shortcuts it steals from the applications running in the terminal. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 482149] F10 as menu shortcut steals it from applications
https://bugs.kde.org/show_bug.cgi?id=482149 --- Comment #2 from Felix Ernst --- I wonder if Konsole could detect if a terminal application reacts to F10 or not and only open the menu when it doesn't. I don't know enough about Konsole to know if that is possible. On the flip side this would mean that any user that is accustomed to F10 to open menu might be surprised that this doesn't work if a certain terminal application is running. However, I think that would be less important than making sure the terminal application works as expected. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 482149] F10 as menu shortcut steals it from applications
https://bugs.kde.org/show_bug.cgi?id=482149 Nate Graham changed: What|Removed |Added Assignee|cf...@kde.org |matt...@mjdsystems.ca Product|frameworks-kwidgetsaddons |frameworks-kconfig Component|general |general -- You are receiving this mail because: You are watching all bug changes.
