Bug 224543

Summary:	Default button does not work for the Categories and Resources sections of the Configure - KOrganizer dialogue.
Product:	[Applications] korganizer	Reporter:	Sabine Faure <sabine>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	CLOSED NOT A BUG
Severity:	normal	CC:	montel
Priority:	NOR
Version:	4.3
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:

Description Sabine Faure 2010-01-27 23:44:54 UTC

Version:            (using Devel)
Compiler:          gcc 4.3.2 
OS:                Linux
Installed from:    Compiled sources

- Launch KOrg
- Go to Settings menu/Configure KOrganizer... and click on the Colors and Fonts icon.
- Change the default color for the Business category in the Categories section.
- Change the default color of one calendar in the Resources section.
- Click on 'Ok'.
- The event created with that category now displays the new color that was picked. And in the Resources/Folders view the color displayed next to the calendar name you picked displays a new color too.
- Now, go back to Settings menu/Configure KOrganizer... and click on the Colors and Fonts icon.
- Click on the 'Defaults' button.

Nothing happens whereas the colors within the Categories and the Resources section should be displaying the default colors.

Trunk, Svn Rev 1081051

Comment 1 Laurent Montel 2010-01-28 12:14:02 UTC

For Category I think that we can reverse color to "color for any category".
But for resource, I don't think that we can create default color.
Color was generated as random, so we can't put default color to it :)

What do you think for category ?

Comment 2 Sabine Faure 2010-01-28 20:39:25 UTC

Following your comment, David explained to me that both the Categories and the Resources use random colors for each new item created so it does not make sense that the 'defaults' button would apply to them. 
And this is probably why it has not been implemented up til now.
So I am closing this bug now.

Comment 3 Sabine Faure 2010-01-28 20:40:16 UTC

Closing this bug.
Trunk, Svn Rev 1081463