Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!samsung!uunet!cbmvax!peter
From: peter@cbmvax.commodore.com (Peter Cherna)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Help with WB 2.0 pulldown hack.
Message-ID: <22679@cbmvax.commodore.com>
Date: 25 Jun 91 14:47:10 GMT
References: <1991Jun24.213319.16123@uokmax.ecn.uoknor.edu>
Reply-To: peter@cbmvax.commodore.com (Peter Cherna)
Organization: Commodore-Amiga, Inc.  West Chester, PA.
Lines: 35

In article <1991Jun24.213319.16123@uokmax.ecn.uoknor.edu> drtiller@uokmax.ecn.uoknor.edu (Donald Richard Tillery Jr) writes:
>
>
>I need some help with a WB 2.0 pulldown I've written:
>
>
>_Description_ (program source included below - THIS IS NOT A GOOD EXAMPLE OF
>               PROGRAMMING, so don't use it as sample code! :-)

How right you are.  I can see scant reason to want to do this.  Workbench
menus are made from the screen's font, as they should be.  That should
hardly bother you, since they're out of sight when not in use, and they're
smart enough to switch to multiple columns in order to fit, should you
choose an extremely large font.

You shouldn't be surprised to find that the menus get re-laid out every
time Workbench is reset.  A change in screen resolution or font does
require it to happen.  There is no good time to jump in and automatically
fudge with the menus either, since the reset happens asynchronously
to the OpenWorkBench() call.

I'll also warn you that not all the menu items contain IntuiTexts, and
there isn't really a guarantee they'll continue to be that way.

I suggest you leave well enough alone.  This sort of programming isn't
really a good idea.

>Rick Tillery (drtiller@uokmax.ecn.uoknor.edu)

     Peter
--
Peter Cherna, Operating Systems Development Group, Commodore-Amiga, Inc.
{uunet|rutgers}!cbmvax!peter    peter@cbmvax.commodore.com
My opinions do not necessarily represent the opinions of my employer.
"Gosh, didn't he have anything positive to say at all?"