Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!rochester!pt.cs.cmu.edu!cadre!pitt!cisunx!ejkst
From: ejkst@cisunx.UUCP (Eric J. Kennedy)
Newsgroups: comp.sys.amiga
Subject: Re: wp crashing
Message-ID: <18030@cisunx.UUCP>
Date: 14 May 89 05:16:36 GMT
References: <8905081520.AA11220@jade.berkeley.edu> <705@solaria.csun.edu>
Reply-To: ejkst@unix.cis.pittsburgh.edu (Eric J. Kennedy)
Organization: Univ. of Pittsburgh, Comp & Info Sys
Lines: 28

In article <705@solaria.csun.edu> ecphssrw@io.csun.edu (Stephen Walton) writes:

>Rick then describes a way to make your machine crash using a very
>obscure combination of reboots, SetFont's and WordPerfect's.  Since
>SetFont is definitely *not* a supported part of the Amiga's OS, but a
>quick hack Dave Haynie put together which works _sometimes_, blaming
>WordPerfect because an interaction between it and SetFont crashes your
>system stretches things a bit.

Yes and no.  If WordPerfect is going to assume that the font it's using
is 8 pixels high, _then_it_should_force_topaz_8_, or some other 8 pixel
font.  If it's going to use the default system font, then it had darn
well better check the size of that font before squashing it into an 8-
pixel-high line.  And WP isn't alone.  Lots of software breaks if you
don't have an 8x8 font as the default.  And you don't have to use
something "obscure" like setfont for this to happen.  Most software
that I've seen that is broken WRT fonts--and this includes WP--will
also break with topaz 9.  You know, the one selectable in Preferences?
The *default* font, for cryin' out loud!  (At least it used to be.)

I've never gotten WP to actually crash because of the system font.  But
I feel the way it responds to non-topaz-8 system font is inexcusable.
And the same goes for lots of other programs.


-- 
Eric Kennedy
ejkst@cisunx.UUCP