| Summary: | Getting "key sequence is ambiguous" even though "Configure Shortcuts" has only one entry for the sequence. | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | Martin Nilsson <ibbles> |
| Component: | general | Assignee: | kdevelop-bugs-null |
| Status: | REOPENED --- | ||
| Severity: | normal | CC: | berndmj, igorkuo, karl, ruro.report |
| Priority: | NOR | ||
| Version First Reported In: | 4.7.1 | ||
| Target Milestone: | --- | ||
| Platform: | Kubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Martin Nilsson
2015-07-07 18:10:31 UTC
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved. This bug is still present, but it’s a bit more complicated than described in the initial report. I tested it using the Norwegian Nynorsk translation (with Norwegian Bokmål as a fallback), which (unfortunately) has *two* menus using ‘V’ as an accelerator: _V_erktøy _V_indu When I assign ‘Alt + V’ to a shortcut, the following happens: The first time I press ‘Alt + V’, the ‘Verktøy’ menu opens. The second time I press it, the ‘Vindu’ menu opens. And the third time I press it, the ‘ambiguous shortcut’ dialogue pops up. (And then it cycles around, so the fourth time I get the ‘Verktøy’ menu again.) Except the error message, this makes sense. So I guess the correct behaviour would be for the shortcut action to be launched on the third (and sixth and ninth etc.) key press, but not on the first or second. But is this a bug in KDevelop or in the global keyboard shortcut feature? *** This bug has been marked as a duplicate of bug 497906 *** (In reply to Bernd from comment #3) > > *** This bug has been marked as a duplicate of bug 497906 *** Why mark this old bug with more detailed description and comment as a duplicate of a new bug? I can still reproduce this bug in KDevelop 6.1.241200. Reopening. |