Bug 338719 - Can't assign keyboard shortcut "ctrl-1" to "email"
Summary: Can't assign keyboard shortcut "ctrl-1" to "email"
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: 4.13.2
Platform: Ubuntu Linux
: NOR minor
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-01 08:17 UTC by Wolf Drechsel
Modified: 2017-01-07 22:37 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
Screen (16.25 KB, image/jpeg)
2014-09-01 08:18 UTC, Wolf Drechsel
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Wolf Drechsel 2014-09-01 08:17:38 UTC
I re-assigned keyboard shortcuts - 
ctrl-0 to overview
ctrl-1 to email
ctrl-2 to contacts
ctrl-3 to calendar
ctrl-4 to news
... and so on.

All this works fine, exept ctrl-1, where to assignment to "overview" does not delete, so whenever I hit ctrl-1, I get the message "The ctrl-1 shortcut is not definite" 


Reproducible: Always

Steps to Reproduce:
1. Asign "ctrl-1" to "email"
2. hit "ctrl-1"
3. 

Actual Results:  
All this works fine, exept ctrl-1, where to assignment to "overview" does not delete, so whenever I hit ctrl-1, I get the message "The ctrl-1 shortcut is not definite" 


Expected Results:  
"email" component comes to th foreground.
Comment 1 Wolf Drechsel 2014-09-01 08:18:33 UTC
Created attachment 88517 [details]
Screen
Comment 2 Wolf Drechsel 2014-09-05 18:13:59 UTC
Sorry, I was not precise enough:
Reassigning ctrl-0 to overview initially works, but is lost after quit&relaunch of Kontact.

I had similar troubles with "apply filter".
Comment 3 Denis Kurz 2016-09-24 19:23:34 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kontact (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 4 Denis Kurz 2017-01-07 22:37:52 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.