Bug 88746

Summary:	"New Messages in (Folder)" in system tray does not switch to Kmail in Kontact
Product:	[Applications] kontact	Reporter:	uli9999 <uli.2001>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED FIXED
Severity:	normal	CC:	m.debruijne, sven.burmeister
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description uli9999 2004-09-03 10:43:28 UTC

Version:            (using KDE KDE 3.3.0)
Installed from:    SuSE RPMs
OS:                Linux

When I am notified of new messages via the Kmail system tray icon, I can right-klick that icon, select "New Messages in..."->"(Folder)", and then Kontact window shows up, and Kmail switches to that folder. This is nice.

However, when Kontact is switched to a different mode (Summary or Calendar, for example), this mode does not change. I think it should switch to Mail mode, as I definitely want to read the new emails at this point.

I think this should be considered as a bug.

Comment 1 Unknown 2004-12-01 18:19:36 UTC

same problem here. If you switch to mail mode manually you can see that the correct folder was chosen but only the program not switched to mail mode.

even more, if selecting a folder with unread mail in the summary, kontact switches to mail mode but always selects the inbox not the chosen folder.
(same thing but viceversa, or should this go into a new but report?)

Comment 2 Michiel de Bruijne 2004-12-03 13:58:46 UTC

same goes for other Kontact plugins (e.g. aKregator) that have an icon in the system tray. I would indeed be nice if the focus is automatically set to the plugin that is activated by clicking the system tray icon. However I don't consider this as a bug but as a usability feature.

Comment 3 Pieter Deelen 2005-03-23 12:30:41 UTC

*** This bug has been confirmed by popular vote. ***

Comment 4 Pieter Deelen 2005-03-23 18:50:58 UTC

In 3.4.0, clicking on a Kontact systray icon (e.g. KMail, aKregator), opens the right plugin.

Comment 5 S. Burmeister 2006-10-28 14:14:05 UTC

As of comment #4, can this be regarded as FIXED?

Comment 6 Anne-Marie Mahfouf 2006-10-28 14:31:41 UTC

I tested it and it's fixed!