Newsgroups: comp.sys.amiga.programmer
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!cunixf.cc.columbia.edu!cunixb.cc.columbia.edu!es1
From: es1@cunixb.cc.columbia.edu (Ethan Solomita)
Subject: Re:  2.0 Compatibility
Message-ID: <1991May4.195340.7179@cunixf.cc.columbia.edu>
Sender: usenet@cunixf.cc.columbia.edu (The Network News)
Nntp-Posting-Host: cunixb.cc.columbia.edu
Reply-To: es1@cunixb.cc.columbia.edu (Ethan Solomita)
Organization: Columbia University
References: <mykes.2036@amiga0.SF-Bay.ORG> <1991Apr30.133904.12649@msuinfo.cl.msu.edu> <mykes.2104@amiga0.SF-Bay.ORG>
Date: Sat, 4 May 1991 19:53:40 GMT

In article <mykes.2104@amiga0.SF-Bay.ORG> mykes@amiga0.SF-Bay.ORG (Mike Schwartz) writes:
>
>Programs that follow the rules in the RKMs *exactly* are already
>having problems with 2.0.  For example, 2.0 allows you to change
>the default screen and window fonts.  Try changing to a 15 point font
>and watch menustrips get screwed up!  The whole point of my posting is
>that there is NO way to maintain compatibility given the direction
>things have and are going.
>
	WRONG. Those programs used NULL for their font rather
than specifically specifying Topaz, which they were told to do.
Everyone assumed that it would never happen. That was their
fault.

	-- Ethan

"Brain! Brain! What is Brain?"