Re: [MiNT] WM_REPOSED implementation

[Evan Langlois <Evan@CoolRunningConcepts.com>]

On Sat, 2005-12-10 at 00:32 +0100, Xavier Joubert wrote:

> Now that I see problems I didn't even envisage before, I guess your method is
> not so bad. Well, it even looks like the /right/ way to handle this...
> 
> The theorical "good way to handling" something often doesn't survive "real
> world". :)

If the problem is old "broken" apps, then they won't be handling any new
messages.  They would still have to rely on some form of hack.  

To say that a new application can use a new REPOSED message is just
silly since the author should be handling the SIZED message properly in
new applications!  REPOSED doesn't fix old apps, and its not compatible
with any other AES, so I see no reason for me to handle a new message
that does exactly what SIZED should be telling me.

If XaAES is intent on sending two messages, then I'll simply update
internal variables, and then do the actual move/resize after a timer. No
flicker, no new messages.