[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-core-devel
Subject: Re: Running kded modules on non-KDE desktops
From: Thiago Macieira <thiago () kde ! org>
Date: 2010-01-10 9:07:15
Message-ID: 201001101007.16111.thiago () kde ! org
[Download RAW message or body]
Em Sábado 9. Janeiro 2010, às 22.47.45, David Jarvie escreveu:
> Applications which use time zone data get the data by calling
> KSystemTimeZones::local(), which in turn gets the system time zone from
> the kded module ktimezoned. This mechanism avoids the system time zone
> being read separately by each application - reading it can be time
> consuming, so fetching it once only is desirable.
>
> This works in the KDE desktop, but when a KDE application is run under
> another desktop environment, ktimezoned isn't running and therefore the
> system time zone returned by kdelibs is always the default, UTC. Is there
> any way for ktimezoned to be activated automatically by kdelibs when it is
> required? If not, it is probably necessary for KSystemTimeZones to read
> the system time zone itself when it is not available from ktimezoned.
I thought kdelibs started kdeinit4, klauncher and kded when necessary.
That isn't happening?
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
Senior Product Manager - Nokia, Qt Development Frameworks
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
["signature.asc" (application/pgp-signature)]
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic