Bug 304843 - subcategory selection by initial letter does not work
Summary: subcategory selection by initial letter does not work
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korganizer
Classification: Applications
Component: incidence editors (other bugs)
Version First Reported In: 4.9
Platform: openSUSE Linux
: NOR minor
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-09 08:35 UTC by Benjamin M
Modified: 2017-01-07 21:27 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Benjamin M 2012-08-09 08:35:22 UTC
Normally, you can navigate the category list in the incidence editor just by pressing the keys corresponding to the initial letters of your categories. For example, if you want to tag an event or task as "family", you open the category list, press "f" and it will take you through all the categories starting with an "f". Ideally, you just push the corresponding key a few times, then push space, and you category is assigned. 

This is extremely convenient! However, it doesn't work with subcategories. I think it must be because the initial letters of subcategories must be recognized as the "tab" key, because subcategories are viewed as indented. 

Reproducible: Always

Steps to Reproduce:
1. Open an event or task and open the categories selection list. 
2. Pick a random category and press the key that corresponds to the initial letter, for example "f" for "family" or "p" for "personal". Do the same with a subcategory. 
3. The category can be conveniently selected by pressing the initial letter key, but the subcategory cannot. 
Actual Results:  
It should be possible to jump to any category, no matter if it is subordinated or not, by just clicking the initial letter key. 

Expected Results:  
It would be great if the subcategories would be treated the same.
Comment 1 Denis Kurz 2016-09-24 18:46:58 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 2 Denis Kurz 2017-01-07 21:27:55 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.