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 563482 - A new Evolution is opened when double-clicking a date in the Clock panel applet
A new Evolution is opened when double-clicking a date in the Clock panel applet
Status: RESOLVED DUPLICATE of bug 317643
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.24.x (obsolete)
Other All
: Normal enhancement
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-12-06 18:22 UTC by Christoph
Modified: 2008-12-10 10:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Description Christoph 2008-12-06 18:22:15 UTC 
It's a minor issue and should be very easy to fix: 

What happens: 
Whenever I click on the "Clock applet" and then double-click on a day, a new Evolution is started. This should not be the default behaviour, because not many people will want several Evolutions running at the same time. 

What should happen: 
1. The applet should check for a running Evolution and:
a. if there is an Evolution running: switch to that window and show the chosen date, or
b. if there is no Evolution running: open one and show the chosen date. 
2. In the preferences of the applet, there should be an option where the behaviour can be changed to today's behaviour (i.e. always proceed according to 1.b).

Ubuntu release: Intrepid (8.10), all updates installed (Dec. 6 2008)
Clock applet: 2.24.1
Evolution: 2.24.2



Distribution: Ubuntu 8.10 (intrepid)
Gnome Release: 2.24.1 2008-10-24 (Ubuntu)
BugBuddy Version: 2.24.1
Comment 1 Paul Bolle 2008-12-10 10:40:11 UTC 
(In reply to comment #0)
> It's a minor issue and should be very easy to fix: 

0) Confirming (surprised me too, the first time). Reclassify as an enhancement (not that that 

*** This bug has been marked as a duplicate of 317643 ***
Comment 2 Paul Bolle 2008-12-10 10:49:35 UTC 
0) Made a mess of my previous comment (decided to mark it as duplicate halfway through).

(In reply to comment #0)
> It's a minor issue and should be very easy to fix: 

1) What I wanted to say was something like: "It is indeed a minor issue, just surprising and/or annoying, but it will probably not be easy to fix. Actually I guess it might require quite some code and moreover it will be rather hard to get the behaviour you'd like without all sorts of usability side effects."