Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!att!bellcore!wind!sdh
From: sdh@wind.bellcore.com (Stephen D Hawley)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Modeless dialogs, what am I doing wrong?
Message-ID: <17224@bellcore.bellcore.com>
Date: 18 Jul 89 18:00:23 GMT
References: <1484@ndmath.UUCP> <14455@dartvax.Dartmouth.EDU> <8029@hoptoad.uucp> <14466@dartvax.Dartmouth.EDU>
Sender: news@bellcore.bellcore.com
Reply-To: sdh@wind.UUCP (Stephen D Hawley)
Organization: Bellcore, Morristown, NJ
Lines: 25

In article <14466@dartvax.Dartmouth.EDU> earleh@eleazar.dartmouth.edu (Earle R. Horton) writes:
>>>What do I have to do to get the cursor to blink normally in the EditText
>>>items of a modeless dialog?
>>(Earle R. Horton) writes:
>>>	DialogPeek xyzzy;	/* Points to your Modeless dialog. */
>>>
>>>	TEIdle(xyzzy->textH);
>>
>>That will work, but a better way is to call DialogSelect in response
>>to null events.  I have philosophical objections to using DialogPeek.
>>After all, why be low level when you can be high level?


DialogSelect() is the way to go.  I just stumbled through this myself.
If you use TEIdle(), it will work, but you will get a mysterious
dot in upper-left corner of each of your edit text items that will not
go away (because, I assume, you are making TEIdle() and DialogSelect()
fight for the same action -technically, this should make no difference,
but it does).


Steve Hawley
sdh@flash.bellcore.com
"1) Never get involved in a land war in Asia and 2) Never go in with a
Sicilian when death is on the line."