Re: [MiNT] XAAES slow?

[Odd Skancke <ozk@atari.org>]

man, 20,.06.2005 kl. 19.46 -0400, skrev Standa Opichal:

> As far as I know yes. At least Arnaud and Me ;)

 Good.

> 
> >  One thing is for sure; wind_calc() can not be used like in WinDom if we
> > want to be able to change themes without restarting the AES. So here we
> > can start discussing solutions....
> 
> Why the way wind_calc() is used in WinDom would make it behave wrong 
> when the window CURR vs. WORK rectangle deltas change? I can fix it.

 Because traditionally wind_calc() is used to figure out the deltas of a
'virtual' window, this call will work with the currently installed
theme. A theme change will also change these deltas and thus cannot be
used on a window that was wind_calc()'ed when the previous theme was in
use. Using wind_set/get() for existing windows will ensure no such
problems, as those work on the window in question, not a 'virtual' one.

> 
> Best Regards
> 
> Standa
> 
> BTW: There is no documentation on the complexity of particular AES call 
> (unlike e.g. in the SGI STL documentation) so I assume the AES does 
> whatever necessary to keep API calls as fast as possible at any point. 
> As allways the comparison point would be n.aes as it is proven to be the 
> fastest (or had been for some here already).

 The whole point of XaAES is to evolve. If the goal of XaAES is to be
n.aes, XaAES is very near completion, and theme changes at runtime is
out of the question. XaAES have a very good reason for its slower
wind_calc(); a standarized easy way for theme modules to tell XaAES the
layout of the window.


 Best Regards,
Odd Skancke