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:48 PM
> To:	MiNT mailing list
> Subject:	RE: [MiNT] XaAES / GEM memory issues
> 
> > 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.
> 
> This only means that the top application, which received the event, must
> reroute the event to proper place after discovering that there is none of
its windows at the place where the user for example clicked. Still this
can be done by the event library (running in user context) and there is no
need to put all this into the device driver. 

But this means that there is no performance gain - the entire idea of doing
this inside the driver is to reduce the number of context switches. By
moving this functionality outside the driver again you basically have XaAES
today...

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.

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