Bug 290212

Summary:	wish: set calendar resource category
Product:	[Frameworks and Libraries] Akonadi	Reporter:	Dj YB <yehielb>
Component:	ICal file resource	Assignee:	kdepim bugs <kdepim-bugs>
Status:	REPORTED ---
Severity:	wishlist
Priority:	NOR
Version:	1.5.3
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed In:

Description Dj YB 2011-12-30 22:04:36 UTC

Version:           1.5.3 (using KDE 4.6.5) 
OS:                Linux

when adding a calendar resource such as iCal, there is no way to distinct it from the other resources inside kontact, if there was a way to add a category to all items in a resource then there was a way.
the purpose of the request is to be able to distinct events from different resources inside kontact.

Reproducible: Always


Actual Results:  
no way to visually distinct events from different resources.

Expected Results:  
a way to distinct events from different resources inside kontact, such as categories.

Thanks

Comment 1 Christophe Marin 2012-02-03 15:37:43 UTC

what do you call 'categories' ?

in recent korganizer versions, a color can be assigned for each calendar resource.

Comment 2 Dj YB 2012-02-04 03:29:26 UTC

the problem is that.
it is possible to assign a colour to a resource, and it is possible to assign a colour to a category.
but then I have all the events coloured according to their categories but some that come from web resources, have no category.
so I can choose to have the colour according to the resource, but then I cant have the category colour.
so there is the option of using both colours, on e inside and one outside, but it is very confusing, not applicable for events with short duration, not so pretty...
so if there was a way to set precedence of category over resource colour, or simply set a category to a resource, or anything like that that would solve the above problem, that would be great!

Thanks,
YB

Comment 3 Justin Zobel 2021-03-09 05:46:26 UTC

Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.