🚀 go-pugleaf

Since I've gottten so much mail on this topic, I thought I'd demo a
recent problem with Frame.  Here's something that I bumped into
recently that crashes Frame 3.0 on a NeXT 2.1 machine:

Go to the References page (this probably works anywhere though) and
turn on snap-to-grid w/ 1/8".  Lay out a frame that is about 3" wide
and 2" high.  Inside the frame, place a line segment of any width.
Place the line segment at the top of the frame after drawing the line
segment. Shrink the frame to use up the most minimal space to hold the
line segment.  If you shrank the bottom or top to make the frame
(essentially) 0" high, then Frame will quit instantly giving you no
chance to save your work whatsoever. It will die because of something
like "locked focus on wrong view" error (it'll be logged in the
Console log). Really incredibly helpful when I used Frame and hadn't
saved in the past 4 minutes and lost all the work.  Now I've got the
auto-save set to one minute.

I didn't think that Frame would die when I originally did this, and I
didn't even do it to "test" Frame, I just thought that since it knew
how high the line segment is (I made mine 3 points high), that it
would make the inside of the frame 3 points high as well.  Alas, it
dies and never saves the work anywhere before it does so.

The other problems that I have had with Frame have been random, hence
I cannot come up with repeatable demos of them, but I have been able
to demo this problem on request.  At first, I thought that my problems
were RAM problems, but all other apps (and the OS as well) work as
expected, so it has to be a Frame problem.
-- 
-- Jeff (jeffo@ux1.cso.uiuc.edu)
-- No NeXTmail please