Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!rutgers!apple!claris!drc From: drc@claris.com (Dennis Cohen) Newsgroups: comp.sys.mac Subject: Re: Suitcase II anomaly Message-ID: <10168@claris.com> Date: 17 May 89 13:52:22 GMT References: <24495@agate.BERKELEY.EDU> <48702@tut.cis.ohio-state.edu> Reply-To: drc@claris.com (Dennis Cohen) Organization: Claris Corporation, Santa Clara CA Lines: 30 In article <48702@tut.cis.ohio-state.edu> Vampire writes: >In article <24495@agate.BERKELEY.EDU> steve@violet.berkeley.edu (Steve Goldfield) writes: >>When I launched it (old MacDraw) with the additional fonts, I noticed that >>the fonts in the document changed; for instance the font menu said I was >>using Camelot. I also had trouble trying to change the fonts; with the very >>long list of fonts, the font size overprinted the list and >>Chicago wasn't visible. > > I have noticed similar problems with "old" MacDraw (pre MacDraw II), >but not just with Suitcase - it happens on any setup with a large number of >fonts. For one reasons or another, MacDraw wasn't able to handle large >font lists. Made for lots of problems when I took MD files made on a floppy >system to be laser-printed on a Mac w/ a HD and gobs of fonts. > The behavior described was typical of the original MacDraw code, done at Apple in the very early days of the Mac. Rather than storing the font name or number, the programmer chose to store the position in the font menu for the objects. If you added or deleted fonts from the Font Menu so that the order changed, you were going to get some very strange results. Even if there had been rules in those days, the programmer could have gone wrong since, at various times, Apple has waffled on whether the font name or number should be the information stored -- currently it is name. -- Dennis Cohen Claris Corp. ------------ Disclaimer: Any opinions expressed above are _MINE_!