Re: [MiNT] WM_REPOSED implementation

[Jo Even Skarstein <joska@online.no>]

> -----Original Message-----
> From: mint-bounce@lists.fishpool.fi
> 
>  I'm gonna tell you a little secret :) XaAES actually already, and have
> always, send a new x/y in SIZED messages when top/left or left borders
> dragged. If you look at the code, you will discover that both the
> WM_SIZED/WM_MOVED pair sent contains the EXACT SAME rectange! What I
> should perhaps try is to send the SIZED first before the MOVED.

Not so sure about this. If you send SIZED first, then the application might crop the window if the new width and height exceeds the limits of the screen. When the window then is moved, you'll not get the desired effect. I think it should be moved first, then resized.

And as I just wrote in my previous mail, when you send the second message, you need to use the new and correct geometry as set by the application following the first message. Sending the same rectangle in both messages will mess things up if the application changes the position or width/height (e.g. cropping to an AES object tree or snapping to a grid).

>  Is Geneva still being supported? I have never actually tested it..

I don't know, I bought it many years ago. I'm using Geneva 008 on my 030 Falcon, but that version was released in the late 90's.

>   3. Send WM_SIZED first, so that the WM_MOVED doesnt make a difference
> when apps treat WM_SIZED 'correcly', and avoid configuration variable.

See above, this might not work.

> > (BTW. for something like this to work smoothly XaAES all per-app options
> > must be configurable on the fly.)
> 
>  They will be. That is, only thing that remains is to implement a
> 'control center' via which such things can be configured.

Sounds good!

Jo Even