Start new session...

Oswald Buddenhagen ossi at
Sun Oct 13 21:57:42 BST 2002

On Sun, Oct 13, 2002 at 02:59:31AM +0200, Martijn Klingens wrote:
> On Saturday 12 October 2002 20:16, Oswald Buddenhagen wrote:
> > as a compromise i modified genkdmconf for now, so it does not
> > automatically add reserve display entries. users that did not notice
> > the feature yet also won't notice now. there are no new users
> > "endangered" and those the already used and liked the feature now
> > have an improved usability.
> With that default value changed the KDE 3.0 behaviour is much less
> dangerous, no?
it is way more "dangerous". you probably weren't "hit" by it, otherwise
you would know. the old behavoiur was simply starting a new xserver 
without any feedback or additional actions required, when the screen was
locked. this can be cool, but mostly it's only very irritating and
annoying, even if you know what is going on.
the problem is, that when i removed this auto-start and did not add an
explicit way to request a new screen, the feature would be effectively
gone alltogether. i don't know how many users already enjoy it, but from
what i've heard, there are quite some.

> but rushing this in so close before
hey, we are not releasing tomorrow. :}

> really really makes me shiver.
from the stability point of view i have no concerns. i'm confident that
the probability that i broke something is much lower than that some
grave bugs are in kdelibs. it's simply close to impossible (even for me
:) to put bugs in that few lines of that simple code. yeah, yeah, famous
last words ... :)
i'm only sorry for breaking the string freeze. but it think it's worth it.

> No matter how much I like your code I also consider the new GUI a
> _new_ feature
that depends on the definition. sure, for kicker & kdesktop this is a
new feature, but for kdebase it's just a moved and usability-wise much 
improved feature.

> and moreover I agree with Ingo and Thomas that the feature is now
> extremely close to people that don't realize the danger until it is
> too late.
this is simply not true. only users that already knew the feature will
be faced with it (and its much improved usability). it's disabled by
default - and as opposed to before, _no_ new user will ever notice it,
if he does not read the kdm readme.

> This stuff either needs a close-to-perfect GUI, or none at all.
well, i tried it without a gui ... but this turned out to be
inacceptable. we need this user's-will-detecting device finally. :)


Hi! I'm a .signature virus! Copy me into your ~/.signature, please!
Chaos, panic, and disorder - my work here is done.

More information about the kde-core-devel mailing list