Re: [MiNT] WM_REPOSED implementation

[Odd Skancke <ozk@atari.org>]

lør, 10,.12.2005 kl. 18.41 +0100, skrev Jo Even Skarstein:
> > -----Original Message-----
> > From: mint-bounce@lists.fishpool.fi
> > [mailto:mint-bounce@lists.fishpool.fi]On Behalf Of Odd Skancke
> > 
> >  Ok, how advanced do we want to make things that infact is dead simple
> > just to give additional meaning to something that was created ages ago?
> > It works beautifully the way it is done now.
> 
> Perhaps I've not fully understood how it works, but if you mean that it works for apps that understand WM_REPOSED it only works for a very few apps. Sending two messages (WM_MOVED then WM_SIZED) for one event (resizing by dragging borders) will cause inconsistencies if you don't consider the applications response to the first message before sending the second.
> 

 Not sure how you mean. But the majority of apps will, upon WM_MOVED, do
things to move the window before going back into the evnt_multi() to get
next queued message. So, in 99% of the cases, the application actually
calls wind_set() to move the window before it reenters its evnt_multi()
at which point it gets the next message waiting for it, which now will
be WM_REDRAWS's generated by the move (if any). WM_REDRAWS have priority
over all other messages in XaASE. Then it gets the WM_SIZED.


 Best Regards,
Odd Skancke