Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!bloom-beacon!apple!tecot
From: tecot@Apple.COM (Ed Tecot)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Modal Dialog update events
Message-ID: <32536@apple.Apple.COM>
Date: 20 Jun 89 01:01:20 GMT
References: <19379@cup.portal.com>
Organization: Apple Computer Inc, Cupertino, CA
Lines: 21

In article <19379@cup.portal.com> nicky@cup.portal.com (nick john pilch) writes:
>I posted a request for help to this newsgroup a few weeks ago.  It concerned a
>problem I was having with the filter proc of a modal dialog.  It was getting too
>many update events, they just wouldn't stop coming.  A coleague was having a
>similiar problem with a dialog he was working on.  Through investigation, some
>trail and error, and help from Mac DTS, we seem to have solved the problem
>although the solution is still non-obvious.
>
>I was drawing the default border for
>the OK button in the filter proc, whenever an update event would come by.
>MacDTS told us that we should rather be doing it with a userItem proc.  That's
>when it hit us that if we did ANY drawing in the filter proc itself, our update
>events got screwed up.  Sure enough, when we took all drawing code out of the
>filter proc and put it into userItem procs, we were cool.  But why?  Why should
>drawing during "filter proc time" screw up our update events?  That's what we'd
>like to know.

I'd guess that your filter proc was returning TRUE, instructing the dialog
manager to not handle the update event.

						_emt