[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-core-devel
Subject: Re: kdebase/kcontrol
From: George Staikos <staikos () kde ! org>
Date: 2003-09-18 16:58:09
[Download RAW message or body]
On Thursday 18 September 2003 06:37, Matthias Kretz wrote:
> I'll try to explain once more what's causing this:
> KControl creates the KCM and only after that it can connect to the
> changed(bool) signal. If a KCM is broken and calls setChanged(true) in the
> ctor the changed(true) signal will not be emitted again until
> setChanged(false) and setChanged(true) is called. To fix this all classes
> using KCModule need to check for KCModule::changed() after the KCM ctor was
> called and enable/disable buttons accordingly.
Here lies the problem. Widgets are created, signals and slots are
connected, load() is called. Load() results in signals, which go to slots,
which setChanged().
--
George Staikos
KDE Developer http://www.kde.org/
Staikos Computing Services Inc. http://www.staikos.net/
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic