Bug 62292 - notifications (balloon, sound, raise window/tab, etc.) configurable per protocol (usability)
Summary: notifications (balloon, sound, raise window/tab, etc.) configurable per proto...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kopete
Classification: Unmaintained
Component: Main Application (other bugs)
Version First Reported In: 0.40.0
Platform: Gentoo Packages Linux
: NOR wishlist
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
: 64433 (view as bug list)
Depends on:
Blocks:
 
Reported: 2003-08-07 03:28 UTC by Michiel de Bruijne
Modified: 2024-09-18 18:26 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michiel de Bruijne 2003-08-07 03:28:02 UTC
Version:           0.7 (using KDE KDE 3.1.2)
Installed from:    Gentoo Packages
Compiler:          gcc-3.2.3, glibc-2.3.2-r1 -march=athlon-xp -O3 -pipe -fomit-frame-pointer
OS:          Linux

I really love the raise window/tab on new messages feature, except when I'm using kopete as an IRC-client.

I'm subscribed to a lot of channels with high volume traffic. When I turn on the raise window/tab on new messages feature and use IRC I cannot work anymore because the chat window is placed on top almost every second. I also use IRC mostly for read only, therefore I like it to stay minimized so I can read it when I want.

For the other protocols (jabber, msn, etc.) I really love the raise window/tab on new messages feature, because these protocols are less (low) volume traffic and mostly read/write. For me this is very nice usability-option.

I know and appreciate that every protocol supported in kopete is treated equally. I'm not requesting to turn off the raise window/tab on new messages feature for IRC, because users with less volume traffic might like this options also with IRC. Therefore I request that the behaviour for notifications (balloon, sound, raise window/tab, etc.) is configureable per protocol.
Comment 1 Thiago Macieira 2003-08-07 07:31:15 UTC
Extending the "look the same" to "sound the same". 

*** This bug has been marked as a duplicate of 56751 ***
Comment 2 Olivier Goffart 2003-08-07 09:27:41 UTC
Eh, this is not the same thing. 
I reopen This bug because i agree with the user.  Raise window on every IRC 
message is a bit anoying. 
That's why i would like to make a difference for this feature. 
 
I don't want to configure this by protocols. but i want to make the difference 
GroupChat/Single chat 
 
Or at least don't raise the windows mor message with a low priority (every message in 
a irc channel has a low priority, exepted highlighted one) 
 
Comment 3 Chris Smith 2003-08-07 11:13:16 UTC
Thats a good idea, perhaps you could only get it to raise on: when your nick is 
said (NickHighlight is already built into kopete) or when you get a /notice or 
a kick or some other things (i.e. bans, exceptions, invites). 
 
Perhaps it could be a sub-option in the IRC protocol configuration to have it 
raise/not raise on important message. This wouldn't be independant of, but 
complimetary to the "Raise window on chat message" in the behaviour tab. 
 
Just a thought. 
Comment 4 Michiel de Bruijne 2003-08-07 14:22:37 UTC
Great suggestion, I like it better than my proposal. If the raise window/tab 
on new messages feature is turned on the window in Single chat is raised 
for every message. If the raise window/tab on new messages feature is 
turned on the window in Group chat is raised only for high priority 
messages. 
 
This applies for every protocol so the application stays constistent and it 
should be easier to implement, because NickHighlight is already built into 
kopete. 
Comment 5 Olivier Goffart 2003-09-17 16:31:10 UTC
*** Bug 64433 has been marked as a duplicate of this bug. ***
Comment 6 Will Stephenson 2004-07-25 11:08:40 UTC
This doesn't affect the raise on new chat; but you can now set custom notifications per contact.
Comment 7 Will Stephenson 2007-11-14 14:24:57 UTC
We now have the insfrastructure to differentiate between IM style chats and chatrooms, so this should be doable
Comment 8 Christoph Cullmann 2024-09-18 18:26:38 UTC
Dear user, unfortunately Kopete is no longer maintained.

Please migrate to another solution, e.g. for Jabber a possibility is Kaidan, for Matrix a candidate is NeoChat.