Path: utzoo!attcan!telly!lethe!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!udel!haven!adm!cmcl2!phri!news
From: roy@alanine.phri.nyu.edu (Roy Smith)
Newsgroups: comp.sys.mac.programmer
Subject: Question about dialog filter procs
Message-ID: <1990Dec21.152707.108@phri.nyu.edu>
Date: 21 Dec 90 15:27:07 GMT
Sender: news@phri.nyu.edu (News System)
Organization: Public Health Research Institute, New York City
Lines: 22


	I don't fully grok what IM-I (page 416) says about using a
filterProc with ModalDialog().  It says:

	A function result of FALSE tells ModalDialog to go ahead
	and handle the event ... NOTE: If you want it to be
	consistent with the standard filterProc function, your
	function should at least check whether the Return key or
	Enter key was pressed and, if so, return 1 in itemHit and
	a function result of TRUE.

	What I don't understand is why you have to check for Return or Enter
yourself and special case them.  If you do nothing at all with keyDown
events and just return FALSE when you get one, with the event unchanged,
won't the default filterProc then do what it usually does?  I guess what I'm
really asking is if your filterProc is just stacked on top of the default
one, or if it replaces it completely?
--
Roy Smith, Public Health Research Institute
455 First Avenue, New York, NY 10016
roy@alanine.phri.nyu.edu -OR- {att,cmcl2,rutgers,hombre}!phri!roy
"Arcane?  Did you say arcane?  It wouldn't be Unix if it wasn't arcane!"