From mint-bounce@lists.fishpool.fi Sat Dec 10 17:58:56 2005 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de Subject: Re: [MiNT] WM_REPOSED implementation From: Odd Skancke To: MiNT List In-Reply-To: References: Content-Type: text/plain; charset=utf-8 Date: Sat, 10 Dec 2005 17:53:56 +0100 Message-Id: <1134233636.29437.151.camel@linuxbox> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-7) X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-To: mint-bounce@lists.fishpool.fi X-original-sender: ozk@atari.org 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.7 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 jBAGwtog027622 lør, 10,.12.2005 kl. 17.27 +0100, skrev Jo Even Skarstein: > > -----Original Message----- > > From: mint-bounce@lists.fishpool.fi > > [mailto:mint-bounce@lists.fishpool.fi]On Behalf Of > > olivier.landemarre@utbm.fr > > > > > 3. Send WM_SIZED first, so that the WM_MOVED doesnt make a difference > > > when apps treat WM_SIZED 'correcly', and avoid configuration variable. > > > > > No you can't try Windom demo, and do it on dialog box in windows, > > it can't work, > > as I already said, because if window is bigger than dialog box, > > after first > > WM_SIZER, Windom will change size to have correct size, then when WM_MOVED > > occur, it not look on size, and put value from gem message, so > > windows size > > will not resize it, and will be too large, so a part of window will not be > > redraw. > > Yes, this is a problem. XaAES will have to wait for the application to call > wind_set on the window before it sends WM_MOVED, and then use the new and > correct width and height. I have no idea if this is easy or hard to > implement, as I have absolutely no knowledge of XaAES internals. 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. Best Regards, Odd Skancke