Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!wuarchive!hsdndev!husc6!unix!mxmora From: mxmora@unix.SRI.COM (Matt Mora) Newsgroups: comp.sys.mac.programmer Subject: Re: Check DialogPtr returned by GetNewDialog? Message-ID: <22891@unix.SRI.COM> Date: 3 Apr 91 16:42:04 GMT References: <1991Apr1.052536.27902@ux1.cso.uiuc.edu> <4143@uakari.primate.wisc.edu> <1991Apr1.224254.5399@neon.Stanford.EDU> <1991Apr2.142214.980@ux1.cso.uiuc.edu> <8690@ucdavis.ucdavis.edu> Reply-To: mxmora@unix.sri.com (Matt Mora) Organization: SRI International, Menlo Park, CA Lines: 30 In article <8690@ucdavis.ucdavis.edu> lim@iris.ucdavis.edu (Lloyd Lim) writes: >In article <1991Apr2.142214.980@ux1.cso.uiuc.edu> dorner@pequod.cso.uiuc.edu (Steve Dorner) writes: >>I agree with Apple in principle; there's a point at which things are SO BAD >>that I don't care what happens anymore. I'm not sure I would have pegged >>GetNewDialog as such a place, though. [stuff deleted] >The only reason I could see this happening in a released app is if someone >fiddling with ResEdit deleted some resources. That shouldn't be the >programmer's fault. This reminds of the discussion a while back on how to >prevent LoadSeg from crashing if a code resource is missing. What do think is better, putting up a window with an error message saying "This application is damaged please reinstall it" or the Bomb Dialog box. Its true its not the programmers fault that the user trashed the resources somehow but at least its the programmers job to try to exit gracefully. But of course all this error checking can become a pain in the butt and make your code more complex than need be. I think ( carefull Apple bashing is comming) Apple should have done a better job at reporting errors from the traps. By the way how does MacApp handle this situation? -- ___________________________________________________________ Matthew Mora | my Mac Matt_Mora@sri.com SRI International | my unix mxmora@unix.sri.com ___________________________________________________________