Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!nrl-cmf!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!hp-pcd!hpcvlo!fred
From: fred@hpcvlo.HP.COM (Fred Taft)
Newsgroups: comp.windows.x
Subject: Re: XRay Text Edit Widget
Message-ID: <3940051@hpcvlo.HP.COM>
Date: Wed, 2-Dec-87 14:23:10 EST
Article-I.D.: hpcvlo.3940051
Posted: Wed Dec  2 14:23:10 1987
Date-Received: Sun, 6-Dec-87 06:40:39 EST
References: <8712011755.AA01008@kvasir.esosun.uucp>
Organization: Hewlett-Packard Co., Corvallis, OR, USA
Lines: 29



Steve,

I know I answered your question yesterday, when we talked on the phone. 
However, since this appears to be a frequent problem encountered by users
of the TextEdit editor, I felt I should also post the solution:


This situation occurs anytime the user clears all characters from a text edit
field, or anytime the first character is typed into a text edit field.  The
text editor has several 'status' events which it will generate when a field
becomes empty or when the first character is typed into a field; certain
applications are interested in knowing when these situations occur, so we
built them into the text editor.  When one of these status events is
generated, the field editor pushes the event on the input queue, and
returns control to the application; the editor views this as a temporary
break, and expects the application to immediately re-invoke it, once it has
completed processing the 'status' event. (A text editor instance is re-invoked
by sending it a MSG_ACTIVATE).

The problem you are experiencing is that you are probably not checking to see
if you receive one of these status events, and thus, you do not re-invoke the
particular text editor instance.  Refer to the section of the text edit
manual page entitled "RETURNED INFORMATION" for the official description
of how this works.


Fred Taft