Path: utzoo!attcan!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!cwjcc!hal!nic.MR.NET!umn-d-ub!umn-cs!hall!rosenkra
From: rosenkra@hall.cray.com (Bill Rosenkranz)
Newsgroups: comp.sys.atari.st
Subject: Re: That little black line
Message-ID: <2524@hall.cray.com>
Date: 12 May 89 19:36:12 GMT
References: <809@stag.UUCP> <1355@laura.UUCP>
Reply-To: rosenkra@hall.UUCP (Bill Rosenkranz)
Organization: Cray Research, Inc., Mendota Heights, MN
Lines: 29


---

on a related note, i just found some odd behavior with AES. my application
does not use a menu bar, at least not all the time. the main screen has
an item which the user can click on. it is very near the top (i.e. top
20 pixels in hi res) so it would normally be in the menu area. i have a
provision to allow users to get at the desk accessories in whihc case
i do the normal

	menu_bar (tree, 1);

etc. all works fine. after the user is done mucking about, i do

	menu_bar (tree, 0);

and redraw the normal screen. the trouble is that now i can't detect button
events near the top of the screen (well, i can if i start with the button
down below the invisible menu_bar and drag into the object). i have tried
editing the resource and changing the size of the menu bar itself, but it
seems like AES is tracking mouse position rather than mouse position IN
THE MENU BAR which is what it SHOULD do.

is there a solution here? would a call to form_dial fix things up?

thanx...

-bill rosenkranz
rosenkra%boston@hall.cray.com