Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!wuarchive!usc!elroy.jpl.nasa.gov!decwrl!pa.dec.com!decuac!haven.umd.edu!wam.umd.edu!dmb
From: dmb@wam.umd.edu (David M. Baggett)
Newsgroups: comp.sys.atari.st
Subject: Re: 3 bombs
Message-ID: <1991May8.043549.21813@wam.umd.edu>
Date: 8 May 91 04:35:49 GMT
References: <1991May7.231318.12305@lsuc.on.ca>
Sender: usenet@wam.umd.edu (USENET Posting)
Organization: University of Maryland at College Park
Lines: 22
Nntp-Posting-Host: cscwam

In article <1991May7.231318.12305@lsuc.on.ca> jimomura@lsuc.on.ca (Jim Omura) writes:
>
>     I've been working on a program for a few months now and it's got
>one "last" problem that I can't fix.  I've been staring at it off and
>on for months now.  The program is graphics oriented using GEM calls.
>As far as I know I've done everything I need to do for a "clean exit"
>back to the desktop.  But I still get 3 bombs when it returns to
>the desktop.  Functionally the program is usable as-is.  But I don't
>like the idea of marketting a product that bombs on exit.  I've
>compiled the program with Sozobon C and I was wonder if this is a
>specific problem with Sozobon.  Or is there something I don't know
>about exiting from GEM?

I had exactly this problem with a GEM application I wrote several years
ago.  In my case, it turned out that one of my menus was too large.  I
think it was 15 lines by 30 characters, which was evidently too big for
GEM to handle.  Making the menu one character shorter fixed it.
(Technically speaking, the "rule" is that menus can't be bigger than
1/4th of the screen.  My menu didn't look that big on the screen.)

Dave Baggett
dmb%wam.umd.edu@uunet.uu.net