avoiding knotify during KDE startup
Lubos Lunak
l.lunak at suse.cz
Wed Sep 15 16:26:58 CEST 2004
On Wednesday 15 of September 2004 15:56, Waldo Bastian wrote:
> On Wednesday 15 September 2004 15:44, Lubos Lunak wrote:
> > The KNotifyDialog change checks if the ksmserver event is disabled, and
> > if yes, turns off starting knotify in startkde. Hmmmm, although thinking
> > of this right now, perhaps knotify startup could be simply always avoided
> > in startkde? KNotifyClient starts the daemon anyway if necessary, and I
> > doubt anybody would notice the delay caused by this with the startkde
> > sound.
>
> Sounds like a cleaner solution indeed. Is there anything that talks to
> KNotify directly without using KNotifyClient?
I don't think so, and I'd consider that broken. KNotifyClient needs to start
the daemon anyway if the app is running outside of KDE, and after all, the
DCOP call is:
void notify(QString,QString,QString,QString,QString,int,int,int,int)
--
Lubos Lunak
KDE developer
---------------------------------------------------------------------
SuSE CR, s.r.o. e-mail: l.lunak at suse.cz , l.lunak at kde.org
Drahobejlova 27 tel: +420 2 9654 2373
190 00 Praha 9 fax: +420 2 9654 2374
Czech Republic http://www.suse.cz/
More information about the Kde-optimize
mailing list