RE: [MiNT] XaAES / GEM memory issues

[Jo-Even.Skarstein@vital.no]

> -----Original Message-----
> From:	Konrad M. Kokoszkiewicz [SMTP:draco@obta.uw.edu.pl]
> Sent:	Wednesday, January 10, 2001 4:26 PM
> To:	Sven Karlsson
> Cc:	mint@fishpool.com
> Subject:	Re: [MiNT] XaAES / GEM memory issues
> 
> > The reason is simple. The device driver will be opened by several
> > processes at once and the device driver code must decide which process
> > that should get the event and you need the windowlist and in practice
> > the cliprectangles for that.
> 
> No, definitely clip rectangles are not needed for that :) The event
> dispatcher just wants to know which application is on the top (regardless
> of the fact whether it is displaying a window or not) and possibly
> maintain a global list of window *handles* to know which window is the
> frontmost, though I am not convinced that it is really necessary. 
> Definitely, it does not matter what are X/Y coordinates of this
> window or its rectangle list.
> 
It does. AES applications can receive mouse events for any window/app, not
just the one on top. This is what the WF_BEVENT flag is for.

Jo Even Skarstein

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

This email with attachments is solely for the use of the individual or 
entity to whom it is addressed. Please also be aware that 
Vital Insurance/DnB Group cannot accept any payment orders or other 
legally binding correspondance with customers as a part of an email. 

This email message has been virus checked by the virus programs used 
in the Vital Insurance/DnB Group.

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *