Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watmath!clyde!rutgers!princeton!udel!rochester!cornell!batcomputer!pyramid!prls!gardner From: gardner@prls.UUCP Newsgroups: comp.sys.mac Subject: Re: MultiFinder programming tip Message-ID: <7838@prls.UUCP> Date: Fri, 4-Dec-87 14:51:18 EST Article-I.D.: prls.7838 Posted: Fri Dec 4 14:51:18 1987 Date-Received: Tue, 8-Dec-87 03:33:56 EST References: <6897@apple.UUCP> Reply-To: gardner@prls.UUCP (Robert Gardner) Organization: Philips Research Labs, Sunnyvale, California Lines: 22 In article <6897@apple.UUCP> han@apple.UUCP (Byron Han) writes: >A tip for MultiFinder friendly programming. >Whenever you call GetNextEvent/WaitNextEvent, you should ALWAYS be >prepared to handle updates and also suspends/resumes. ALWAYS. >You should always use keyDownMask + updateMask at the very least, >and including app4Mask as well is desirable. >If you do not include updateMask, you will "drop" update events which is >unsightly confusing and bad. If you do not include app4Mask, you will >drop suspend/resumes. This is bad. This sounds like a Multifinder bug. It also sounds like a pain. Somewhat related, I have a GetNextEvent gripe that's been bothering me: I would like to be able to get only events associated with a given window. Is there some way of doing this? Perhaps with EventAvailable or something and still guarantee that you remove only proper events from the queue? Robert Gardner