Bug 191024 - kopete notification of first incoming message not configurable in "Notifications-Settings"
Summary: kopete notification of first incoming message not configurable in "Notificati...
Status: REPORTED
Alias: None
Product: kopete
Classification: Applications
Component: Main Application (show other bugs)
Version: unspecified
Platform: FreeBSD Ports Unspecified
: NOR wishlist
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-29 12:28 UTC by Christof Schulze
Modified: 2009-07-05 06:01 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christof Schulze 2009-04-29 12:28:16 UTC
Version:            (using KDE 4.2.2)
Installed from:    FreeBSD Ports

The notification of the first incoming message of a conversation is less configurable then the follow ups.

I do not like popups so I use urgent hints of my window manager to notify me of new  messages in a chat. This only works on follow up messages not on the very first one.
It seems like kopete assumes that the message window is being popped up on the current virtual desktop which is not the case.
Thus I often miss that there are incoming messages unless people write me two messages at once.

Imho two fixes are possible:

* if the action "receiving first message in a conversation" is configurable with all the other notifications. There one could set the flag for setting urgent hints whenever a first message to a conversation is received

* if the action "receiving first message" would also trigger the "incoming message" that is already configurable in the notification.
Comment 1 Christof Schulze 2009-06-09 21:03:45 UTC
as a follow up:

I can understand the thinking behind the fact that there is no notification done when the conversation window (MainWindow#2) is created because the window manager already knows about a change because the window appeared.

Yet not being able to define a notification for the messages starting a new conversation that get opened in a new tab within that window is bad because that was I constantly miss messages.

Maybe there is a third alternative: treating each message that is received by window and not by tab.

That way, no new configuration option would be introduced and the user would get notified uniformely with each message that is opened within a window (even if having multiple conversations in tabs of a window).