Fwd: Re: Turning off screensavers [xarafaxz at nxxx: KMplayer feature request]

[Olivier Goffart]

Le Jeudi 12 Janvier 2006 18:25, David Faure a écrit :
> On Thursday 12 January 2006 18:10, Lubos Lunak wrote:
> > class KDE_EXPORT KScreenSaver
> > {
> > public:
> >     /**
> >       * docs here
> >       */
> >     void setEnabled( bool set );
> > };
>
> Yes; well, namespace [or static method] if the class isn't supposed to be
> instanciated.
>
> >  Isn't that a bit ... silly? Not that I really mind if this is really the
> > way it's intended to be, but won't we end up with hundreds of things like
> > this?
>
> Well, I wouldn't say hundreds, but all kapp->startServiceBy... have moved
> to KToolInvocation, for instance, so yes, it's intended to be classes with
> a particular purpose as opposed to KApplication being the all-in-one mess.
>
> But maybe the screensaver enabling/disabling is part of a bigger set of...
> desktop operations? Right now I can't think of other similar things that
> app might want to do.

Like i said, Kopete does need to know when the screen is locked/unlocked in 
order to go away
(we actually connect to kdesktop/KScreensaverIFace/KDE_start_screensaver)

so we have already at least 3 method in our KScreenSaver or KDesktop namespace

there are certainly more.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20060112/b75d4d2c/attachment.sig>