Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!mcsun!unido!infbs!tubsibr!hafer
From: hafer@tubsibr.uucp (Udo Hafermann)
Newsgroups: comp.sys.atari.st
Subject: wind_update (Was: Re: AES bug?)
Message-ID: <1989Dec19.150145.13851@tubsibr.uucp>
Date: 19 Dec 89 15:01:45 GMT
References: <150@bucsb.UUCP> <1113892203364652@thelake.UUCP>
Sender: hafer@tubsibr.uucp (Udo Hafermann)
Organization: TU Braunschweig, Informatik (Bueltenweg), Germany
Lines: 13

steve@thelake.UUCP (Steve Yelvington) writes:

>MWC documents wind_update() as "an AES routine that locks or unlocks a
>window." In "Atari ST Application Programming" (Pollack and Weber, Bantam
>Books), wind_update() is documented as "communicate with the AES about the
>application's current processing," which is more general and more
>accurate. 

What exactly happens when an application makes multiple calls to
wind_update()?  Are these calls stacked (as with hide_mouse())?  Is
there a way to find out how many calls have been made, or to force an
undo of all stacked calls?