Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!julius.cs.uiuc.edu!ux1.cso.uiuc.edu!pequod.cso.uiuc.edu!dorner From: dorner@pequod.cso.uiuc.edu (Steve Dorner) Newsgroups: comp.sys.mac.programmer Subject: Re: MultiFinder vs WDEF Keywords: MultiFinder, WDEF, major switch Message-ID: <1991Jan4.150838.13108@ux1.cso.uiuc.edu> Date: 4 Jan 91 15:08:38 GMT References: <47731@apple.Apple.COM> Sender: news@ux1.cso.uiuc.edu (News) Organization: University of Illinois at U-C Lines: 30 In article <47731@apple.Apple.COM> stevec@Apple.COM (Steve Christensen) writes: >It won't let you switch because the standard WDEF (ID=0) varCode 1 is the >modal dialog window. Normally if a modal dialog is the front-most window, >you don't want to allow switching because a critical operation needs to be >completed. I wonder about that. When I put up a modal, I'm usually trying to inform the user that has happened, or trying to get some piece of information my program needs before it can do what the user has asked it to do. "Sorry, disk full." "Sorry, malformed address." "Please enter your password:" "Please configure me:" I see no reason in any of these cases NOT to allow switching. In fact, I can't think of a SINGLE SPOT in my program where it would hurt the user to switch, and several where it could be beneficial. So I've hacked (and I mean hacked) my filterProc to always allow switching. I can hear some of your knees jerking out "you shouldn't use modals!" I'm afraid I can't agree. Users expect them for error conditions, and it also makes perfectly good sense to use them for obtaining vital info. I would like to see the "don't switch on modals" restriction simply REMOVED. -- Steve Dorner, U of Illinois Computing Services Office Internet: s-dorner@uiuc.edu UUCP: uunet!uiucuxc!uiuc.edu!s-dorner