Bug 124678 - Change the system tray icon colour
Summary: Change the system tray icon colour
Status: RESOLVED UNMAINTAINED
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: 1.2.2
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: triaged
: 144391 207816 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-04-01 00:20 UTC by gen2l
Modified: 2017-01-07 21:24 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description gen2l 2006-04-01 00:20:12 UTC
Version:           1.2.2 (using KDE 3.5.2, Gentoo)
Compiler:          gcc version 3.4.5 (Gentoo 3.4.5-r1, ssp-3.4.5-1.0, pie-8.7.9)
OS:                Linux (i686) release 2.6.14-gentoo-r7

Change trayicon color.
The bad visible counter new news.
Sorry for bad english.
Comment 1 Teemu Rytilahti 2006-12-16 05:06:25 UTC
I actually agree with this. Looks like I currently have 1535 unread articles, but it doesn't show up clearly. Imho we should watch and see what kind of systemtray we're going to have in KDE4 and decide what to do with this.
Comment 2 Frank Osterfeld 2006-12-16 14:23:46 UTC
> Looks like I currently have 1535 unread articles

Which shows that the unread counter in its current form is completely useless for people having more than only a few feeds.
Comment 3 Pino Toscano 2007-04-19 00:51:44 UTC
*** Bug 144391 has been marked as a duplicate of this bug. ***
Comment 4 Maciej Pilichowski 2007-04-19 22:19:56 UTC
"
Of course it is a matter of personal taste, but in hires akregator icon plus number (and two different colors), well it is all cluttered in small space. So the main wish is -- remove counter. 
 
But as a further suggestion -- there could be only two icons: 
 
* current akregator in gray -- for akregator running without any unread news 
* current akregator in color -- with news (at least one new message), without counter on it 
 
For number counter notification is better place. 
"
Comment 5 Risto H. Kurppa 2007-05-09 23:26:59 UTC
How about letting user to set number X in the options:
colour one (green): no messages
colour two (orange): 1 - X messages
colour three (red): more than X messages

And no, I don't suggest those colours but just as a hint to clear what I mean. I also have often several hundred unread messages but if it's under 1000 I still can see the number because smaller font size than the default is.

r

Comment 6 Gene Seto 2008-11-25 21:05:19 UTC
Triaged. Tried to test on r887704 but I can't tested this since I do not have a functional system tray.

Hum
Comment 7 Dotan Cohen 2008-12-29 14:55:43 UTC
I agree with Maciej's suggestion in comment #4. What is important is _if_ there are new messages, not how many. Users will open the app when they have a new message, not when they have x>=n new messages.
Comment 8 ultrabla 2009-04-25 04:06:05 UTC
when i expect more stuff to come in i wait for x>=n :)

well i would like to have another background colour for system tray :)
Comment 9 Dotan Cohen 2009-04-25 11:54:28 UTC
@muh2000: why did you remove all the CC addresses from the bug? Please do not do that. I suggest that you now email the CC'ed users and ask if they would like to be readded to this bug. The list of removed addresses is here:
https://bugs.kde.org/show_activity.cgi?id=124678
Comment 10 ultrabla 2009-04-25 12:01:42 UTC
@dotan cohen.

i am sorry. i am not rly familiar with this bug tracking system and thought it would just remove the notification of my post and not of the complete bug report :(
(i thought my post was not that important that it would require another mail in somebody's mailbox...)

i re added all the mail now since it was the original setting.
Comment 11 Christophe Marin 2010-02-22 00:11:18 UTC
*** Bug 207816 has been marked as a duplicate of this bug. ***
Comment 12 Denis Kurz 2016-09-24 19:38:19 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of akregator (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 13 Denis Kurz 2017-01-07 21:24:01 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.