Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!wuarchive!mit-eddie!snorkelwacker!usc!sdd.hp.com!apollo!caip.rutgers.edu!rutgers!uwm.edu!cs.utexas.edu!uunet!mcsun!ukc!axion!edc!fraser
From: edc!fraser@caip.rutgers.edu (Fraser Orr)
Newsgroups: comp.windows.x.motif
Subject: Problems with XmText
Message-ID: <4c15aa3b.20b6d@apollo.HP.COM>
Date: 8 Aug 90 09:06:00 GMT
References: <2676@network.ucsd.edu> <5686@hplabsz.HPL.HP.COM> <8962@jpl-devvax.JPL.NASA.GOV>
Sender: root@apollo.HP.COM
Reply-To: edc!fraser@caip.rutgers.edu (Fraser Orr)
Organization: Atex European Development Centre, Livingston, Scotland
Lines: 9
Resent-From: nazgul@alphalpha.com (Kee Hinckley)
            e-Id:  <9008081413.AA06027@alphalpha.com>
To: comp-windows-x-motif@rutgers.edu
Resent-To: motif-tmp@alphalpha.com
Resent-Date: Wed, 8 Aug 90 10:13:14 EDT


Does anyone have an idea why the XmText widget beeps at me whenever I
set the doit flag to False in an XmModifyVerifyCallback?  I have even
gone so far as to switch the bell off, but it still beeps at me!
Strangely, it works fine appart from this annoying little foible.
According to Douglas Young's new book, this flag is supposed to be
False by default, but mine is always set True unless I change it.

Thanks for any help,

==Fraser Orr <fraser@edc.uucp> +44 506 416778x206
UseNet: {uunet,sun}!atexnet!fraser JANet: fraser%edc@cs.hw.ac.uk