Bug 364968 - show event location in agenda view if there is enough free space
Summary: show event location in agenda view if there is enough free space
Status: REPORTED
Alias: None
Product: korganizer
Classification: Applications
Component: agendaview (weekview) (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 207810 (view as bug list)
Depends on:
Blocks:
 
Reported: 2016-07-01 09:04 UTC by Tom Mittelstädt
Modified: 2023-09-18 05:12 UTC (History)
4 users (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 Tom Mittelstädt 2016-07-01 09:04:04 UTC
Korganizer's agenda view should show the event location if there is enough free space in a block.

Reproducible: Always
Comment 1 eemantsal 2016-07-08 12:22:27 UTC
+1
A thumbnail with an OSM frame that when clicked would open Marble centered in the corresponding location would be great.
Theres a similar proposal for Kaddressbook in the forum: https://forum.kde.org/viewtopic.php?f=83&t=133716

I think KDE lacks a bit of more integration between it's own "family". It's a shame, because most of the "infrastructure" is there since many years ago. So, please, devs, this kind of things make users' lifes much easier and are very "eye catchy" for attracting new users. Consider to implement it.
Comment 2 Glen Whitney 2016-10-05 22:54:51 UTC
Presumably just the text of the Location field would be much easier and would go 98% of the way to making folks happy about this. Ideally, the fields that go in the agenda view would be configurable in much the way that the header fields that go in the message list are configurable in Kmail.  But as a start, just a checkbox in the configure korganizer panel for the agenda view which toggles "show location" would be super and that is already 90% of the functionality, in practice.  If anyone is able to do this, it would be a great enhancement to KOrganizer.  Thanks!
Comment 3 gjditchfield 2022-05-08 22:35:02 UTC
*** Bug 207810 has been marked as a duplicate of this bug. ***