About the clock...

[Benjamin Meyer]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday 27 June 2003 8:29 am, Andras Mantia wrote:
> On Friday 2003 June 27 11:11, Benjamin Meyer wrote:
> > On Friday 27 June 2003 3:58 am, Andras Mantia wrote:
> > > Hi,
> > >
> > > With the new changes the clock configuration is a little screwed up. I
> > > run CVS HEAD usually, but sometimes switch back to BRANCH. I have my
> > > clock set to Digital with LCD look in HEAD. When I start 3.1, I see a
> > > Fuzzy clock. I set to digital and when I go back to HEAD I see a Plain
> > > clock. I set to digital, but the LCD look setting is lost. It seems to
> > > be a real backwards compatibility problem and doesn't look professional
> > > at all.
> >
> > Yup, that one config needs to be transitioned and I simply haven't gotten
> > around to it yet because it isn't a simple task.
>
> I saw that you've made a commit regarding the config file update. I don't
> know if that was supposed to fix it or not, but it doesn't seem good to me.
> It's ok that on an upgrade it will convert the settings, so you see the
> same clock as you have configured in KDE 3.1.x, but the users (developers)
> who switch between KDE 3.1.x/HEAD will still have broken clocks, as the
> possible values for Type have changed. I know that the compability is
> backwards compability, but for me this would be the first case when I
> notice that the config entries are causing a mess in an older version after
> upgrading to a new one. And when I change the settings again in 3.1.x, the
> kconf_update script will not be run when I restart CVS HEAD and thus I will
> have again a "broken" clock. And I think the problem will be present in
> case of larger networks with different KDE version (3.0, 3.1, 3.2) on them,
> but sharing the same config dir and depending on which one you will log in,
> the clock will be different.
>
>  If the commit was only to do an update and you anyway wanted to take care
> about the above issues, please forgive me for making noise.

Yah, that was pretty much all it was suppost to do.  "kconf_update is a tool 
designed to update config files."  I don't think kde has ever supported conf 
files for users that go back and forth between two different versions.

- -Benjamin Meyer

- -- 
Public Key: http://www.csh.rit.edu/~benjamin/public_key.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE+/OH31rZ3LTw38vIRAoN+AJ9C2is3dUGvWCSX0GFloMW9sWT24wCeKx4u
wC5y0VIBdIoeaP7xP2cxr6U=
=Eggc
-----END PGP SIGNATURE-----