Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!rutgers!mcnc!rti!dg-rtp!dg-rtp.dg.com!blumer
From: blumer@dg-rtp.dg.com (Todd Blumer)
Newsgroups: comp.windows.x.motif
Subject: Re: Grey-ing things out
Keywords: stippled sensitive
Message-ID: <1990Sep13.185713.12667@dg-rtp.dg.com>
Date: 13 Sep 90 18:57:13 GMT
References: <7876@gollum.twg.com> <21340002@hpopd.HP.COM>
Sender: usenet@dg-rtp.dg.com (Usenet Administration)
Reply-To: blumer@dg-rtp.dg.com (Todd Blumer)
Organization: Data General Corporation, Research Triangle Park, NC
Lines: 31

I have experienced two problems with XtSetSensitive() (or XmNsensitive)
under Motif 1.0.1.

First, setting XmNsensitive to False on PushButtonGadgets will cause the
push button to change size (that is, the buttons previously had their
size explicitly set).

Second, using the XmNsensitive resource on text widgets can sometimes
cause a sigsegv or sigbus.  I did not take the time or effort to
identify the exact sequence of events that caused the sigsegv, but
it went something like:

	type a value into the text box
	set XmNsensitive to False
	...
	set XmNsensitive to True
	change the value in the text box
	... <do some other things> ...
	upon creation of a new text widget, (buried somewhere in the Motif
		library code), a sigsegv occurs.

Has anyone else seen either of these problems?  Do you have a good
solution?  For the text widget, I just made a label describing the
text to be "greyed" and set XmNeditable on the text widget to False.
The sigsegv went away.

--
Todd Blumer (blumer@dg-rtp.dg.com   ...!mcnc!rti!dg-rtp!blumer)
Data General Corp.
Research Triangle Park, NC  27709
(919) 248-6338