Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!decwrl!labrea!polya!kaufman From: kaufman@polya.STANFORD.EDU (Marc T. Kaufman) Newsgroups: comp.sys.mac.programmer Subject: Re: MultiFinder switch bug with custom WDEFs Message-ID: <2792@polya.STANFORD.EDU> Date: 10 May 88 03:55:24 GMT References: <242@uvabick.UUCP> <8700@apple.Apple.Com> <2887@midas.TEK.COM> <9332@apple.Apple.Com> <2770@polya.STANFORD.EDU> <9442@apple.Apple.Com> Reply-To: kaufman@polya.Stanford.EDU (Marc T. Kaufman) Organization: Stanford University Lines: 33 Keywords: MultiFinder doesn't allow switching when it thinks it sees a dBoxProc In article <9442@apple.Apple.Com> dwb@apple.UUCP (David W. Berry) writes: > Making a dialog modeless is really a lot easier than people >seem to think. Basically, you put the following code into your event >loop: [14 lines of code] > which corresponds to the part of the modal dialog which looks >like: [5 lines of code] Well, yes but. More interesting is that you seem to be telling me that Multifinder looks for dBoxProcs, and doesn't care about windowkind, and that IsDialogEvent looks at windowkind, and doesn't care about dBoxProcs. If so, then one can have a layered application-modal dialog (e.g. one that uses the ModalDialog call) without disabling task switching?? Or does the ModalDialog event loop preclude switching. I think the original point (in an article that must have expired by now) was that LOTS of applications have Alerts, etc., that have been coded with ModalDialog, that COULD be changed to modeless if everyone took the time to do it, but that have existed lo these many years just fine until Multifinder. If they can be made to layer properly by RezEditing the WDEF entry in the DLOG resource, fine. By the way: it may suprise you to know that there are useful Mac tools that don't have event loops, but still occasionally need to put up simple dialogs. It WAS nice not to have to code an event loop... (sigh!). Marc Kaufman (kaufman@polya.stanford.edu)