Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!sun-barr!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!hoptoad!tim
From: tim@hoptoad.uucp (Tim Maroney)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Modeless dialogs, what am I doing wrong?
Message-ID: <8064@hoptoad.uucp>
Date: 19 Jul 89 22:34:48 GMT
References: <5331@ipl.jpl.nasa.gov>
Reply-To: tim@hoptoad.UUCP (Tim Maroney)
Organization: Eclectic Software, San Francisco
Lines: 55

In article <5266@ipl.jpl.nasa.gov> dfs059@ipl.jpl.nasa.gov (Dan Stanfill)
writes:
>NO!  While that may work, for a modeless dialog, IsDialogEvent() handles the
>cursor blinking.

tim@toad.com (Tim Maroney) writes:
>No, I'm sorry, but if you'd taken the ten seconds to consult Inside Mac
>before you posted this, you'd have seen that IsDialogEvent does no such
>thing.  It is DialogSelect that will do the cursor blinking on a null
>event.  IsDialogEvent by itself will do exactly nothing.

In article <5331@ipl.jpl.nasa.gov> dfs059@ipl.jpl.nasa.gov (Dan Stanfill)
writes:
>Well, instead of the ten seconds Mr. Maroney took to consult his manual,
>I actually read it.  Inside Mac I-416 says under IsDialogEvent:
>
>  Warning:  If your modeless dialog contains any editText items, you
>  must call IsDialogEvent (and then DialogSelect) even if GetNextEvent
>  returns FALSE; otherwise your dialog won't receive null events and
>  the caret won't blink.

As you've pointed out in another message, this in fact says that
DialogSelect is necessary -- and if you had taken the two seconds
necessary to turn the page and read the note under the DialogSelect
routine, you would have seen this spelled out in words of one
syllable.

>I have verified with the debugger that
>indeed DialogSelect is not called except in response to an actual user
>event, thus it is clearly IsDialogEvent which causes the caret to blink.

Which turned out to be false.  DialogSelect was indeed called in
response to null events.  One wonders whether the mention of the
debugger data was a deliberate fabrication.

>Also, responses such as "if you'd taken the ten seconds to consult Inside
>Mac..." are ridiculously juvenile and uncalled for on a forum in which 
>people are trying to help others.

No, Mr. Stanfill, they are not.  I grow increasingly tired of people
who post messages to the network on technical subjects without
bothering to spend a miniscule amount of time checking their statements
in the references.  I have very right to point this out.  What is
juvenile and uncalled for is to defend a demonstrably false point by
shouting "NO!", misreading references, providing specious debugger
data, and impugning the personalities of those better informed than
yourself.  You had the minimal decency to correct your technical
errors in a later message, but rather than apologize for your personal
attacks, you reaffirmed them explicitly.  It is you who lowered the
conversation to this level; I have been quite circumspect throughout.
-- 
Tim Maroney, Mac Software Consultant, sun!hoptoad!tim, tim@toad.com

"Every institution I've ever been associated with has tried to screw me."
	-- Stephen Wolfram