From mint-bounce@lists.fishpool.fi Sat Dec 10 18:54:15 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 18:50:42 +0100 Message-Id: <1134237042.29437.158.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.8 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 jBAHsE6U019643 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