On Mon, 16 Oct 2000, Allan Rae wrote:
> So the question is:
>
> Do you _really_ need to disable the various fields when the dialog is
> readonly or will disable OK and Apply suffice?
>
> Remember that when switching to a readonly buffer, toggling readonly on or
> opening a readonly file the user gets a message dialog saying "Document is
> readonly -- you won't be able to change anything" or something to that
> effect. So the user has already been warned that they can't expect to do
> much to the document.
>
> The only cases I can think of that need to have objects disabled are where
> a particular objects callback can cause some change to the document (such
> as the documentclass combo in FormDocumentı) but that can sometimes be
> blocked in the callback by checking the readonly status either of the
> buffer directly or of the bc_. In the documentclass case it needs to be
> disabled.
>
> Allan.
>
IMHO this argument sounds like you are arguing from an ease of
implementation rather than an ease of use point of view. I think things
should be always disabled if they cannot be changed, unless they are
simply view-type things - this should be an invariant across the UI.
just my 2 farthings
john
--
"Whereof one cannot speak, thereof one must be silent."
- Wittgenstein
