Version: (using KDE KDE 3.3.2) Installed from: Compiled From Sources Compiler: gcc 3.4.3 OS: Linux I find the notifications (the sounds I set) very irritating when I'm away/playing a game and I think that there should be a function to disable notifications when set to away.
You mean like the checkbox that says "Enable events while away" under behaviour->notifications?
Heh. Maybe rename this to "Enable notifications while away".
The problem with this checkbox is: Disabling "Log to file" or/and "Print a message to standard error output" notifications while away is a very bad idea as noone would expect this behaviour, a log file and stderr messages are (and so should be) completely independent from user interface affecting notifications. The solution: Add notifications special to the online state or create log files or/and stderr messages independently from knotify.
On Sunday 06 March 2005 9:06 am, kde@bugs.jan.ritzerfeld.net wrote: > 14:06 ------- The problem with this checkbox is: Disabling "Log to file" > or/and "Print a message to standard error output" notifications while away > is a very bad idea as noone would expect this behaviour, If you want message logging, use the history plugin. Don't know why you would ever want to be using KNotify for this. > a log file and > stderr messages are (and so should be) completely independent from user > interface affecting notifications. No, they aren't. That is the entire point of the whole KNotify API.
Jason Keirstead wrote: > On Sunday 06 March 2005 9:06 am, kde@bugs.jan.ritzerfeld.net wrote: >> 14:06 ------- The problem with this checkbox is: Disabling "Log to file" >> or/and "Print a message to standard error output" notifications while away >> is a very bad idea as noone would expect this behaviour, > > If you want message logging, use the history plugin. Message logging? History? I'm talking about knotify's "Print a message to standard error output" and stderr messages respectively! These messages aren't the content of arrived messages. They look like this: KNotify Mo Mär 7 14:32:33 2005: Bar ist jetzt Online. > Don't know why you would ever want to be using KNotify for this. Is it possible to write a log file beside using knotify? >> a log file and >> stderr messages are (and so should be) completely independent from user >> interface affecting notifications. > > No, they aren't. That is the entire point of the whole KNotify API. Log files and stderr messages don't affect the GUI. It's fact. Why didn't you even quote/discuss my suggested solutions? "Add notifications special to the online state or create log files or/and stderr messages independently from knotify." Despite the log/stderr issue, the first one is IMHO the most consistent way to disable notifications while away, at the moment there are two places controlling notification behavior, a very confusing way. BTW, your focusing on knotify as the solution for every problem ("Honestly I am getting really sick of all these notification bug reports from people who don't know what you can do with KNotify.", Bug 65019) lead me to knotify's "Log to file:".
Sorry, this (my) statement is wrong: "These messages aren't the content of arrived messages." is not completely right, an "only" was missing. Should be "These messages aren't only the content of arrived messages." Bad English though. Anyway, message content logging is just one notification of many.
I still don't see why you want this. If you want to know when people came online or offline, use the statistics plugin. If you want to see a logfile of a conversation, use the history plugin. Even for some reason you want this, then *don't* disable notifications while away, turn off the sounds for all cases, and in your external script fire your own sound / message if you are not away. You are asking for very custom advanced behaviour that IMO is way outside the scope of what Kopete needs to provide.
> I still don't see why you want this. I just want a good old plain log file. Or a sort of. I didn't find a way to get one beside knotify and its action "Log to file". After reading some bug reports I thought using knotify is the proposed way to get a basic one. But the various exceptions of event firing render some of knotify's notification methods useless: Stop writing a log/printing msgs to stderr when the user changes his status to away doesn't make any sense to me (like the X server would stop logging when the screensaver engages). > [...]. > You are asking for very custom advanced behaviour that IMO is way outside the > scope of what Kopete needs to provide. Well, this is exactly why I think a log file is helpful. It lets a non kde devolper create his own very advanced customizations in e.g. perl by parsing the log.
On Monday 07 March 2005 4:15 pm, kde@bugs.jan.ritzerfeld.net wrote: > Well, this is exactly why I think a log file is helpful. It lets a non kde > devolper create his own very advanced customizations in e.g. perl by > parsing the log. But you can already do this.. like I said, just enable notifications while away, and you are off to the races.
> But you can already do this.. like I said, just enable notifications while > away, and you are off to the races. Bug/Wish 100967. Nonetheless, I find the "Enable events while away" checkbox inconsistent/contradictory to some knotify notification actions. You don't do. Agree to disagree?