Bug 235771 - incomplete labels for color usage options for to-dos
Summary: incomplete labels for color usage options for to-dos
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: LO normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-29 23:33 UTC by Sabine Faure
Modified: 2017-01-07 22:47 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sabine Faure 2010-04-29 23:33:18 UTC
Version:            (using Devel)
Compiler:          gcc 4.3.2 
OS:                Linux
Installed from:    Compiled sources

- Launch Korg
- Create a new event, a new to-do and a new journal for today using different calendars and different categories for each.
- Check that they are correctly displayed on the month view 
- Go to Settings menu/Configure KOrganizer...
- Click on 'Views' icon and go to the 'Month View' tab
- Select the first radio button 'Category inside, calendar outside'
- Click on 'Apply'

On the to-dos the inside coloring radio button options (first two) never apply since the coloring depends on how late the to-do is due whereas all four radio buttons work fine with events and journals.

So I think that for the first two radio buttons the labels should be edited in something like this:

* Category inside, calendar outside 
(except for to-dos for which inside color is linked to its lateness) 
* Calendar inside, category outside
(except for to-dos)

Trunk, Svn Rev 1120671
Comment 1 Denis Kurz 2016-09-24 18:51:56 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 22:47:51 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.