Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!sdd.hp.com!hplabs!hplabsz!mayer
From: mayer@hplabsz.HPL.HP.COM (Niels Mayer)
Newsgroups: comp.windows.x.motif
Subject: Re: Problems with XmText
Message-ID: <5756@hplabsz.HPL.HP.COM>
Date: 8 Aug 90 18:23:36 GMT
References: <2676@network.ucsd.edu> <5686@hplabsz.HPL.HP.COM> <8962@jpl-devvax.JPL.NASA.GOV> <1490@edc.edc.UUCP>
Reply-To: mayer@hplabs.hp.com (Niels Mayer)
Organization: Hewlett-Packard Labs, Software & Systems Lab, Palo Alto, CA.
Lines: 28
Summary:
Expires:
Sender:
Followup-To:

In article <1490@edc.edc.UUCP> fraser@edc.UUCP (Fraser Orr) writes:
>Does anyone have an idea why the XmText widget beeps at me whenever I
>set the doit flag to False in an XmModifyVerifyCallback?

I consider this a bug in Motif 1.0. I think it has been fixed in Motif 1.1.

>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.

I think that is an error in Doug's book. Here are my notes (extracted from
some source I wrote) on this:

* Note that the text callbacks are "weird" in that they expect values in
* the callback structure to be set inside the callback proc to determine
* what actions need to be taken after the callbackproc returns. In
* particular, the XmTextVerifyCallbackStruct's 'doit' slot is always set to True,
* and must be set to False if the callbackproc doesn't want the action to be
* taken.

-------------------------------------------------------------------------------
	    Niels Mayer -- hplabs!mayer -- mayer@hplabs.hp.com
		  Human-Computer Interaction Department
		       Hewlett-Packard Laboratories
			      Palo Alto, CA.
				   *