[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MiNT] XaAES doesn't respect wind_update?



Jo Even Skarstein wrote:


form_dial doesn't block anything, but a form_dial()-session is usually
inside a wind_update. So if XaAES respected wind_update it wouldn̈́'t be
possible to run wind_dial-apps without them blocking all other apps.


The single TOS form_do implies wind_update.
So the normal form_dial/form_do/form_dial sequence does not
need additional wind_update. That is where XaAES does not lock
other applications. XaAES keeps track of this sequence.
It might even keep track of spurious surrounding wind_updates by
the calling application. The AES of course, knows who is locking.
The calling application is suspended in the form_do so there
will be no screen output from the caller and it can safely
put the stuff in a window and leave other apps unlocked.

However, because the other applications are not locked, the
AES must lock whenever it itself writes something to the screen.

--
Groeten; Regards.
Henk Robbers. http://members.chello.nl/h.robbers
Interactive disassembler: TT-Digger;  http://digger.atari.org
A Home Cooked C compiler:      AHCC;  http://ahcc.atari.org