From mint-bounce@lists.fishpool.fi Sat Dec 10 00:00:26 2005 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de Message-ID: <1134168954.439a0b7a48c89@webmail1.utbm.fr> Date: Fri, 9 Dec 2005 23:55:54 +0100 From: "olivier.landemarre@utbm.fr" To: mint@fishpool.com Subject: Re: [MiNT] WM_REPOSED implementation References: <1134166727.439a02c7bec16@imp1-g19.free.fr> In-Reply-To: <1134166727.439a02c7bec16@imp1-g19.free.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 User-Agent: Internet Messaging Program (IMP) 3.2.8 X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-To: mint-bounce@lists.fishpool.fi X-original-sender: Olivier.Landemarre@utbm.fr Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: X-Virus-Scanned: by amavisd-new at relay.boerde.de X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on relay.boerde.de X-Spam-Status: No, hits=1.0 tagged_above=-50.5 required=7.0 tests=AWL, BAYES_00, RCVD_IN_SORBS X-Spam-Level: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by wh58-508.st.uni-magdeburg.de id jB9N0QZC017285 Selon Xavier Joubert : > Hi AES hackers, > > > Selon Jo Even Skarstein : > > You can always add the option to tell the AES to send first MOVED and then > > SIZED to specific applications, but that will only work if XaAES can be > > externally configured on per-application basis (like Geneva can). I don't > > know if this is possible, as I can't get XaAES to run on my Milan yet. > > A good way of handling this (IMHO) would be, when AES needs to move and > resize a > window at once to send : > 1- a WM_SIZED message with the new coordinates (new X and new Y included), > then > 2- a WM_MOVED message with the same coordinates. I do exactly this actually except I prefer WM_MOVED before WM_SIZED, this what I do on CVS, and it work not so bad, in official 0.70 version I do only WM_MOVED. In your case I know application that don't like it, for example Qed and windows dialog in Windom, and there is other, I test only some softwares. In case of Qed, with WM_SIZED it will change with and height to have a mod8 or mod16 for this value, and recalculate sliders, then you put WM_MOVED with width and height you wan't but not new width and height that application wan't, Qed will put it directly but not change his size nor recalculate slider, this a very small problem in fact. For Windom case this is stronger because position will be good but size can be totaly wrong, because on WM_MOVED it not look for new size, so if window is bigger than dialog, other part of window will not redraw at all, because it correct size only on WM_SIZED. So prefer WM_MOVED before WM_SIZED. Olivier