[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-devel
Subject: Re: UI Inconsistency OK APPLY buttons
From: Thomas Reitelbach <tr () erdfunkstelle ! de>
Date: 2003-03-31 20:56:18
[Download RAW message or body]
On Monday 31 March 2003 21:45, Andras Mantia wrote:
> On 2003. March 31., Monday 23:29, Waldo Bastian wrote:
> > On Monday 31 March 2003 20:09, Andras Mantia wrote:
> > > On 2003. March 31., Monday 19:03, Willy De la Court wrote:
> > > > one addition OK only store changes when something is changed e.g.
> > > > when Apply is active When Apply is inactive OK just leave the dialog.
> > > > This prevents the dual restart of the panel when you click Apply to
> > > > activate the changes and when you click OK just after that it
> > > > restarts the panel again which is stupid.
> > >
> > > Just for the note: and Cancel cancels the changes also in case when
> > > Apply was pressed before. So in any case after you pressed Cancel the
> > > state of your application/dekstop/whatever should be the same as before
> > > the dialog appeared.
> >
> > No, this is not the case.
>
> Yes, in this case Cancel behaves in a different way => it's confusing. I
> know this is not KDE's fault, and actually it makes sense the current
> implementation, but it's simply not consistent. I just saw in the QT
> Designer manual:
> "Click Apply to accept changes to the listbox widget. Click OK to leave the
> dialog once the changes have been accepted. Click Cancel to leave the
> dialog without saving any changes."
Yes, this is how it behaves right now.
> I think this is the rule we follow, but the explanation is confusing, since
> you don't know if clicking on Cancel will not save any changes since the
> dialog appeared or since the last time you've pressed Apply.
I don't know any user that has any problems with this, really. Users are used
to it on linux, windows, mac, i guess everywhere. IMO this should not be
changed.
Thomas
[Attachment #3 (application/pgp-signature)]
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic