Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!shadooby!samsung!usc!apple!voder!parns!michael
From: michael@parns.nsc.com (Michael C. Wagnitz)
Newsgroups: comp.windows.x
Subject: Re: bug in Xaw asciiStringWidget
Keywords: Xaw asciiStringWidget keyboard actions loss
Message-ID: <167@harley.nsc.com>
Date: 15 Nov 89 00:52:38 GMT
References: <2566@goanna.oz.au>
Reply-To: michael@parns.nsc.com (Michael C. Wagnitz)
Organization: National Semiconductor Corporation, Santa Clara
Lines: 24


In article <2566@goanna.oz.au> dmh@goanna.oz.au (Darren Hosking) writes:
+ The version of xfig I have (1.4.3, X11 patchlevel 6) has a problem inputing
+ text AFTER almost any option in the popup menu (right button) is selected.
+ Text input works fine when xfig is first started but once, say, save is
+ selected in the popup menu you cannot input text. The text input prompt
+ and cursor appear when you click where you want the text but anything
+ typed is not echoed.
+ 
+  [stuff deleted]
+ 
+ I have followed through the code and it appears that after using the popup
+ menu keyboard events are not reported.
+ 
+  [more stuff deleted]

I too have been experiencing 'intermittent' loss of keyboard actions in one
asciiStringWidget in my application.   Button actions remain active, but
keyboard actions stop being delivered.  The actions can usually be restored
by deleting a particular popup menu created during execution.  I say usually,
because sometimes the effect does not seem to be related to creation/deletion
of that popup.  Only one (of 4) of the asciiStringWidgets used in my
application is ever affected by this 'bug', and never consistently.  Unlike
the above sender, my X11R3 has all nine patches applied.  Solution anyone?