[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Running kded modules on non-KDE desktops
From:       David Jarvie <djarvie () kde ! org>
Date:       2010-01-09 21:47:45
Message-ID: 201001092147.46128.djarvie () kde ! org
[Download RAW message or body]

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.

-- 
David Jarvie.
KDE developer.
KAlarm author -- http://www.astrojar.org.uk/kalarm


[prev in list] [next in list] [prev in thread] [next in thread]