Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!samsung!think!ames!uhccux!munnari.oz.au!murtoa.cs.mu.oz.au!rob
From: rob@cs.mu.oz.au (Robert Wallen)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Simulating a Menu Bar with Pop-Up Menus
Message-ID: <2880@murtoa.cs.mu.oz.au>
Date: 1 Dec 89 13:36:27 GMT
References: <9095@hoptoad.uucp> <1989Nov28.053644.28100@agate.berkeley.edu>
Reply-To: rob@murtoa.UUCP (Robert Wallen)
Organization: Comp Sci, Melbourne Uni, Australia
Lines: 18

In article <1989Nov28.053644.28100@agate.berkeley.edu> lippin@math.berkeley.edu writes:
>I don't think there's a good way to do this; Apple either doesn't want
>it to be easy or is just being lazy.

On a related issue.  Has anyone worked out how to hack the PopUpMenuSelect so
that it doesnt present the users with that stupid blank rectangle and the
scroll arrow if it is too close to the edge of the screen.

The best I have been able to do is ask the MDEF what the size of the 
rectangle is going to be and adjust the 'initial item' that PopUpMenuSelect
will be over but have found weird behaviour with this as well.  Some pixel
positions seem to generate different rectangles to others.  Anyone out there
have any clues?

I did see a message once from someone at Symantec claiming that they had
solved the problem by some sort of stub MDEF that called the standard. However,
the last time I checked Think C still had the problem (move a window close to
the bottom of the screen and hold option down while clicking the title bar.)