Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!uunet!cbmvax!ken From: ken@cbmvax.commodore.com (Ken Farinsky - CATS) Newsgroups: comp.sys.amiga.programmer Subject: Re: 2.0 Compatibility Message-ID: <21276@cbmvax.commodore.com> Date: 6 May 91 14:21:18 GMT References: <1991Apr30.133904.12649@msuinfo.cl.msu.edu> <1991May4.195340.7179@cunixf.cc.columbia.edu> Reply-To: ken@cbmvax.commodore.com (Ken Farinsky - CATS) Organization: Commodore, West Chester, PA Lines: 20 In article <1991May4.195340.7179@cunixf.cc.columbia.edu> es1@cunixb.cc.columbia.edu (Ethan Solomita) writes: >In article mykes@amiga0.SF-Bay.ORG (Mike Schwartz) writes: >>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 >> > 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. Well, partly wrong. While an application can set the font for the MenuItems, it cannot set the font for the Menu. That is, items in the top menu must use the screen's title bar font. The 1.3 manual shows how to properly lay-out these items in the current font. The example is available on one of the fish disks. -- -- Ken Farinsky - CATS - (215) 431-9421 - Commodore Business Machines uucp: ken@cbmvax.commodore.com or ...{uunet,rutgers}!cbmvax!ken bix: kfarinsky