Version: (using KDE KDE 3.2.3) Installed from: Debian testing/unstable Packages OS: Linux I am feeling a need for a new event type in the notifications page. It would be nice if there was an event for a new chat starting. i.e. the opening of a chat window, or the addition of a chat tab. This would mean that when one is out of the room, you can hear that someone has sent you a new message. This is different to the event on incoming message, as once I'm chatting I don't want a noise on every line, just to let me know that a new chat has started. Thanks.
I second this request, as I do not want to hear a sound on every message that arrives but only when somebody tries to start a new chat.
There is already a KNotify event for when someone initiates a new conversation. But this only works if the message queue is enabled - it is fired when a new event is placed on the queue. Apparantly this bug reporter wants the event to work when you have the queue disabled as well.
The following notifications are in my list for 0.9.0 on 3.3.0 * A contact has come online * A contact has gone offline * A contact's online status has changed * A highlighted message has been received * A message marked with a low priority has been received * An incoming message has been received * An outgoing message has been sent * New email has arrived in your MSN inbox * New email has arrived in your Yahoo inbox * Sound notification for Kopete events Which of these is the one you indicate "There is already a KNotify event for when someone initiates a new conversation"? The closest is "An incoming message has been received". Also you say that it only works if the message queue is enabled - I have the following ticked: Settings->Behaviour->Miscellaneous->Use the message queue And there is no change in the notifications available. You are correct however, that I do believe this should work whether the queue is enabled or not.
On October 14, 2004 08:31 am, Andy Parkins wrote: > Which of these is the one you indicate "There is already a KNotify event > for when someone initiates a new conversation"? The closest is "An > incoming message has been received". "Sound notification for Kopete events" I know the label is horrible, but that is what it is. > Also you say that it only works if the message queue is enabled - I have > the following ticked: Settings->Behaviour->Miscellaneous->Use the message > queue If you have the queue enabled, the above event occurs when a user starts a new conversation only.
It does not work for me. The sound is not played when the notification-bubble, asking to start or ignore the chat, appears.
> If you have the queue enabled, the above event occurs when a > user starts a new conversation only. As this is not the case, this is not a wishlist item but a bug. Or shall I file another one?
*** Bug 87786 has been marked as a duplicate of this bug. ***
Still valid for KDE Beta1 3.4
I'm giving this my "vocal" vote.. since I've split up my others already.
*** This bug has been confirmed by popular vote. ***
Very much needed!
*** Bug 111480 has been marked as a duplicate of this bug. ***
Agreed. I would really like to see this fixed too. Currently, I've tied the incoming message notification to the following shell script, which works sometimes, and might be useful to other bug reporters in the meantime. But, this is slow, unreliable, and unnecessarily resource-hungry. Something built into kopete that only triggers on new messages (and is correctly labelled and intuitive) would be a great help. -------------------------------- #!/bin/sh LAST_TIMESTAMP_FILE=~/.last_msg_timestamp #SOUND_FILE=/usr/share/sounds/Kopete_Received.ogg #PLAYER="ogg123" SOUND_FILE=/usr/share/sounds/KDE_Notify.wav PLAYER="bplay" FMT=%Y%j%H%M NOW=`date +${FMT}` HOUR=`date +%H` if [ -e $LAST_TIMESTAMP_FILE ]; then LAST=`cat $LAST_TIMESTAMP_FILE` else LAST=0 fi DIFF=`expr $NOW - $LAST` if [ $DIFF -gt 5 ]; then # don't play if it's after midnight -- msgs aren't THAT important :) if [ $HOUR -gt 8 ]; then $PLAYER 2>/dev/null >/dev/null "$SOUND_FILE" else echo "Sleeping time; won't play" fi else echo "Hasn't been five minutes since last message; skipping." fi date +${FMT} > $LAST_TIMESTAMP_FILE --------------------------------
i am wondering if someone is working on it. i cant find anything new in dev-0.12 for this problem.
*** Bug 150157 has been marked as a duplicate of this bug. ***
*** Bug 117511 has been marked as a duplicate of this bug. ***
*** Bug 123735 has been marked as a duplicate of this bug. ***
This issuse is still valid with KDE 4.3, Kopete 0.80.2. The sound notification for kopete events item has vanished.
*** Bug 126859 has been marked as a duplicate of this bug. ***
This seems fixed in at least 4.6.2. There are two notifications for incoming messages: one for when the message comes from the active window and another for when it does not. So you just need to disable the sound in the former notification.
I don't completely agree with your analysis, I think the idea was to have a notification when a new chat was started! So for example, I don't want notification from an already opened chat that is in the background… ! No?
Let me be clear what problems I have that Kopete didn't (perhaps it does now with 4.6.2, I haven't tried it yet) solve: I am watching TV with my laptop on and in the same room, but not in use -- it's sitting on a table with the screensaver running. - Someone wants to chat with me. How would I know? I couldn't use notifications previously, because even when I was sat in front of the computer, everytime they typed anything I get constant noises. - Someone I was chatting with 2 hours ago, comes back online and says something. I have walked away from the computer and the screensaver has kicked in. How do I know they are waiting to speak? The solution, to me, seems obvious, and my mobile phone implements the algorithm correctly, but Kopete never has: If a chat opens or a new line is received AND my screensaver is active (or perhaps simply Kopete has auto-awayed) then make a noise. If the mouse is moving around on the screen, then don't make a noise, just pop up a notification. Noises are there for when I can't see the screen, but my attention is needed. But noises when I can see the screen are an annoyance.
(In reply to comment #22) > Let me be clear what problems I have that Kopete didn't (perhaps it does now > with 4.6.2, I haven't tried it yet) solve: > > I am watching TV with my laptop on and in the same room, but not in use -- it's > sitting on a table with the screensaver running. > > - Someone wants to chat with me. How would I know? I couldn't use > notifications previously, because even when I was sat in front of the computer, > everytime they typed anything I get constant noises. > - Someone I was chatting with 2 hours ago, comes back online and says > something. I have walked away from the computer and the screensaver has kicked > in. How do I know they are waiting to speak? > > The solution, to me, seems obvious, and my mobile phone implements the > algorithm correctly, but Kopete never has: > > If a chat opens or a new line is received AND my screensaver is active (or > perhaps simply Kopete has auto-awayed) then make a noise. If the mouse is > moving around on the screen, then don't make a noise, just pop up a > notification. > > Noises are there for when I can't see the screen, but my attention is needed. > But noises when I can see the screen are an annoyance. This is a different scenario that has not been mentioned on this bug entry before. Kopete does not do that, I think no KDE program interacts to the screensaver in that way as far as I know. Ok, re-open this bug then.
I didn't mean to say that it definitely has to be tied to the screensaver. It would be sufficient to be linked to Kopete's auto-away state. The screensaver is not a good choice of indicator anyway, as presumably some people will disable the screensaver, but might still walk away from the computer. I think it has to be: noises when kopete thinks I'm "away".