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

List:       kde-devel
Subject:    Re: KConfig still having issues?
From:       Mosfet <mosfet () jorsm ! com>
Date:       1999-05-26 17:54:29
[Download RAW message or body]

I added a bunch of debug warnings and you are right, they are being read
correctly. Looking at my code I was relying on KConfig::hasKey() to determine if
there is a widget specific color entry. It seems that in the old KConfig if
there is a blank key hasKey() returned false. Now if the key exists at all it
returns true. 

I am not sure which is the proper behavior. Should KConfig::hasKey return true
even if the key has no value? In the old KConfig it did not, and that saves the
programmer from having to check if the key is blank and invalid manually.

Either way, sorry about being on the wrong track about the colorGroup and
numEntry stuff. Since everything was turning out black I just assumed that was
it ;-)

On Tue, 25 May 1999, pbrown@redhat.com wrote:
> On Wed, 26 May 1999, Mosfet wrote:
> 
> > Okay, thanks. If you need to see the exact code I am using take a peek at
> > kdeui/kthemebase.cpp's  KThemeBase::readConfig. The readEntry stuff works, but
> > none of the other readXXX stuff is anymore.
> 
> I just tested out readColorEntry and readNumEntry right in this routine,
> and I am not seeing any problems.
> 
> Are you sure you are up-to-date?  Check your config files for
> corruption...they may be corrupted if you used stuff from early yesterday
> and you had i18n'ed entries.
> 
> ---
>   Preston Brown                                    Systems Engineer
>   pbrown@redhat.com                                Red Hat Software, Inc.
--
Daniel M. Duley - Unix developer & sys admin.
mosfet@kde.org
mosfet@jorsm.com

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