Am Freitag, 21. September 2001 10:12 schrieb Allan Rae:
> So the user might notice something changed by a flash of a text input
> changing or a radio button toggling and wonder: "Did I really see
> something change? If so, which one was it?"
>
> With a warning message or some other feedback they'd know they will
> get changed entries. As it is we have surprises. Sure, you can
> argue that the auto reset button is off by default and that it should
> be clear that something will be automatically reset but think about a
> newbie and how they will react and how they use software. They/we/I
> usually don't read manuals until all else fails. They/we/I push
> buttons blindly hoping that one of them will do what they/we/I want
> it to do.
>
> Even if we can't tell them which entries have changed (or which are
> about to change) we can at least warn them (or confirm for them) that
> something did/will change.
Well, yes... But a warning message does not solve this IMHO. I can only
tell you how I used it as a newbie (not long ago). I always confirmed
that question without thinking about the results. I'm too lazy to think
about that, and confirming is always the best if you have no idea. I
thought something like "yes, of course it has to be reset, otherwise it
probably won't work!?" (quite stupid, isn't it?). With the button, *I*
would be a little more careful and try to find out what that button's
for before activating anything.
> I think I'd be inclinded to just get rid of the auto-reset and let
> the user push the "class options: reset" button if they really want
> them reset.
After I knew what Reset to Default means, I began to be very annoyed by
the popup. I don't want to be asked over and over again, I hate to
repeat myself, I want to decide once. And that's the idea behind the
"Autoreset" button. I can decide that class change should always mean
"Reset to Default". I tell that once and no question will keep annoying
me anymore. I don't have to press "Reset" each and any time. Maybe I'm
just lazy, but that's my opinion of efficient working. Personally I'd
really miss the autoreset possibility.
And do you think that the user will press the "Reset" button more
reflected than the "autoreset" checkbox? Or the "Save as Defaults"
button (which is *much* more dangerous)? I don't see why this checkbox
should be more dangerous than a lot of other checkboxes in LyX. And you
can't popup a message on each of this checkbox "Do you really know what
you are doing? Read the manual on this button first!", can you?
Jürgen
(of course there should have been a lot of smileys in this message, but
I begin to get used to the rules of this list)
> Allan. (ARRae)
