Xref: utzoo comp.windows.x.motif:1800 comp.windows.x:32199 comp.windows.misc:1780
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!mcsun!i2unix!esacs!ferrara
From: ferrara@esacs.UUCP (Giancarlo Ferrara)
Newsgroups: comp.windows.x.motif,comp.windows.x,comp.windows.misc
Subject: read_only vs sensitive vs unsensitive
Keywords: unsensitive, read_only
Message-ID: <83@esacs.UUCP>
Date: 1 Feb 91 14:00:44 GMT
Followup-To: comp.windows.x.motif
Organization: Esa Software s.r.l. Rimini (FO), ITALY
Lines: 26


I have some problem about ui and i hope someone can help me.

The only way that X provide to disallow modification made by the user
on some widget (toggle, option menu,..) is "set_unsensitive".
Some time the value in toggle have no meaning in the context when it's
made unsensitive, some time have a meaning but the program want just
a read_only field.

Really a widget can assume three states:
enable (I/O field)
READ_ONLY (readable, with some feedback to avoid that the user thinks
          that is a program bug that he is not able to modify)
really_disable (not allows change and also is greyed out to mean:
         "user, do not care about any value you can find, have
          no meaning in this context"

Motif allow read_only just for text but it do not have any user-feedback
between enable and read-only;
No one widgets set i know have read_only toggle.

I want to know if there is a "common used" way to provide this feedback

Thanks,
Giancarlo
..!mcsun.EU.net!i2unix!esacs!ferrara