After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 201396 - Display local/base times in day view
Display local/base times in day view
Status: RESOLVED DUPLICATE of bug 205804
Product: evolution
Classification: Applications
Component: Calendar
1.5.x (obsolete)
Other All
: Normal minor
: Future
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on: 201390 201393
Blocks: 341452
 
 
Reported: 2001-02-20 22:45 UTC by Federico Mena Quintero
Modified: 2009-06-15 13:09 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Federico Mena Quintero 2001-02-20 22:45:17 UTC 
The day view needs to display the local time and base ("other timezone") times
for appointments.
Comment 1 Damon Chaplin 2001-07-31 23:56:44 UTC 
What did you mean by this exactly? Does it have to be in 1.0?

In most views space is really tight, so we couldn't display
both times in the view. But maybe in a tooltip or something.
(Same goes for #1397)
Comment 2 Federico Mena Quintero 2001-08-01 02:34:19 UTC 
The day view already shows the local times of the appointment because
of the hour grid lines.  It would be nice to have the "base time"
values shown somewhere, perhaps a tooltip or in the status bar when
the mouse is over the appointment.
Comment 3 Federico Mena Quintero 2001-08-03 20:07:30 UTC 
Same as #1397.
Comment 4 Damon Chaplin 2001-08-09 01:29:52 UTC 
Changing to Future/Minor. I don't think we have time for 1.0.
Comment 5 André Klapper 2004-09-02 11:04:39 UTC 
still valid for evolution1.5-1.5.91.0.200407250730-0.snap.ximian.8.1.
the same as bug 201397.
adding keyword.

btw: displaying both times has been realized in the mailer.
Comment 6 Milan Crha 2009-06-15 13:09:14 UTC 
Marking as a duplicate of the newer because it contains committed fix for this.

*** This bug has been marked as a duplicate of 205804 ***