Bug 305207 - There is no more keyboard shortcut for editing the task/event category combobox or achievement slider element
Summary: There is no more keyboard shortcut for editing the task/event category combob...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korganizer
Classification: Applications
Component: incidence editors (show other bugs)
Version: 4.13
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-15 16:31 UTC by Alexandre Bonneau
Modified: 2017-01-08 19:33 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
Current incidence editor with no keyboard shortcuts assigned by default (66.96 KB, image/png)
2012-08-15 18:25 UTC, Alexandre Bonneau
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alexandre Bonneau 2012-08-15 16:31:27 UTC
Since a few korganizer version, to be exact since the last major ui change in the incidence editor, you can't use any keyboard shortcut to select the category combobox or the achievement slider (eg. on the French configuration alt+i for accessing the title filed, alt+l for the place (cf. screencapture)).

Reproducible: Always

Steps to Reproduce:
1. Add a new task
2. using only your keyboard, try to directly access the category combobox
Actual Results:  
you can't.

Expected Results:  
Being able to use something like alt+c to put the focus on the category combobox
Comment 1 Alexandre Bonneau 2012-08-15 18:25:46 UTC
Created attachment 73192 [details]
Current incidence editor with no keyboard shortcuts assigned by default
Comment 2 Denis Kurz 2016-09-24 18:43:35 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 korganizer (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 3 Denis Kurz 2017-01-07 22:14: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.
Comment 4 Alexandre Bonneau 2017-01-08 19:33:50 UTC
Reopened as #374769