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

In article <11767@well.UUCP> shf@well.UUCP (Stuart H. Ferguson) writes:
>Is SetFont really buggy -- or lets say, not fully reliable?  I've been

Well, not really.  I haven't noticed problems with SetFont itself.  The
problem is the programs that assume the default font is 8x8.  Of which
WordPerfect, Dirmaster, Comm (and many term programs derived from it),
vt100 (at least an older version), Blitz, and Less are just a few.

>trying to write a program that will work with whatever the system font
>is and I've been testing it with SetFont.  It seems that about half the
>time SetFont will crash if I use it *after* running my program.  It
>always works before I run my program (i.e. right after a reboot), so I
>just assumed it was something I was doing.  But if SetFont is flakey,
>perhaps that's the reason, not my code.

It's been quite awhile since SetFont has crashed on me, and I use it
quite a bit because of certain unmentionable programs.  I'd keep
checking your code...

Oh, setfont and fed (the font editor) are a bad combination.  Actually,
fed + anything is a bad combination.

-- 
Eric Kennedy
ejkst@cisunx.UUCP