Tickets :: Comment on [#12989] Missing: entry category/tag color; time in monthly view

* Your Email Address
* Spam protection	Enter the letters below: .__..__ .__ .__ __ \| \|[ __[__)[__)/ ` \|__\|[_./[__)\| \__.
Comment	>> In H3 the calendar shows a fine overview with a color pro category >> and the event time from .. to in the monthly overview. In Horde 5.1.3 >> the calendar overview is confused, because the event color and the >> event time are missing. > > There is no per-event coloring currently in Horde 5. Categories were > replaced by tags. There is already an open enhancement request about > adding colored event "dots" to the event bubbles for the event tags' > color. > >> In Horde 5.1.3 I have to write in the subject the event time. So I >> see at least the start time in the monthly overview. > > Already possible again in Kronolith 4.2 > >> The definition of several calendars is impossible, because the sync >> with Android supports only one calendar. Is'nt it? > > You can absolutely define multiple calendars in Kronolith. In Horde > 5.1/Kronolith 4.1 and prior, all events are "multiplexed" into a > single calendar to sync. Starting in 5.2/4.2 it will be possible to > truly sync multiple sources, but not every client supports it. > >> To work fine with the calendar again it's necessary: >> >> - to show the defined tag-color in monthly/weekly/daily overview >> * has a event several tags, the color of the first tag is winning >> - to show the event start-end-time in the monthly overview. > > See the many mailing list and tickets that already discuss this. > >> Otherwise the calendar is unfortunately a step backwards. > > That's a blatant generalization. If it's THAT important for you than > consider sponsoring the feature to be developed. > >> For example: >> The google calendar shows the start time and an color point for every entry. >> In Outlook I can defined several categories for an event. Outlook >> shows the color of first defined category. > > Again, see the various mailing list discussions and tickets. The > suggestion of just adding the "first" tag is not feasible for a > variety of reasons.
Attachment
Watch this ticket

Saved Queries