Article View: comp.sys.atari.st
Article #39733Re: wind_update (Was: Re: AES bug?)
From: Derek Mui
Date: Wed, 20 Dec 1989 18:35
Date: Wed, 20 Dec 1989 18:35
29 lines
1522 bytes
1522 bytes
> 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?
Wind_update() must be called in ON and OFF sequence. It doesn't
matter how many times you call it as long as they are called in that
sequence. Sorry, there isn't any way to find out how many times you have
made that call.
Wind_update() should be called when you are going to do a lot
of screen update and you don't want to be interrupted in the middle of
the operation. The best place to call wind_update( 1 ) is right after
the event_multi(). Make sure to call wind_update( 0 ) before you entering
back to the event loop.
==================================================================
Derek Mui, Atari Corp, 1196 Borregas Ave, Sunnyvale, CA 94086
UUCP: {..ames!atari!mui}
FAX: 408-745-5179
Disclaimer: Opinions expressed here are my own and they may be
hazardous to your mind.
==================================================================
Technical Details
Message-ID:
<1907@atari.UUCP>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!sun-barr!newstop!sun!imagen!atari!muiReferences:
<1989Dec19.150145.13851@tubsibr.uucp>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!sun-barr!newstop!sun!imagen!atari!mui From: mui@atari.UUCP (Derek Mui) Newsgroups: comp.sys.atari.st Subject: Re: wind_update (Was: Re: AES bug?) Message-ID: <1907@atari.UUCP> Date: 20 Dec 89 18:35:52 GMT References: <1989Dec19.150145.13851@tubsibr.uucp> Organization: Atari Corp., Sunnyvale CA Lines: 29