From mint-bounce@lists.fishpool.fi Sat Dec 10 03:54:07 2005 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de Subject: Re: [MiNT] WM_REPOSED implementation From: Evan Langlois To: Xavier Joubert , mint@fishpool.com In-Reply-To: <1134171157.439a141589d71@imp1-g19.free.fr> References: <1134166727.439a02c7bec16@imp1-g19.free.fr> <1134168954.439a0b7a48c89@webmail1.utbm.fr> <1134169484.29437.97.camel@linuxbox> <1134171157.439a141589d71@imp1-g19.free.fr> Content-Type: text/plain Date: Fri, 09 Dec 2005 20:49:28 -0600 Message-Id: <1134182968.25322.15.camel@taro.coolrunningconcepts.com> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - esc14.midphase.com X-AntiAbuse: Original Domain - fishpool.com X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - CoolRunningConcepts.com X-Source: X-Source-Args: X-Source-Dir: X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-To: mint-bounce@lists.fishpool.fi X-original-sender: Evan@CoolRunningConcepts.com 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_01, RCVD_IN_SORBS X-Spam-Level: * On Sat, 2005-12-10 at 00:32 +0100, Xavier Joubert wrote: > Now that I see problems I didn't even envisage before, I guess your method is > not so bad. Well, it even looks like the /right/ way to handle this... > > The theorical "good way to handling" something often doesn't survive "real > world". :) If the problem is old "broken" apps, then they won't be handling any new messages. They would still have to rely on some form of hack. To say that a new application can use a new REPOSED message is just silly since the author should be handling the SIZED message properly in new applications! REPOSED doesn't fix old apps, and its not compatible with any other AES, so I see no reason for me to handle a new message that does exactly what SIZED should be telling me. If XaAES is intent on sending two messages, then I'll simply update internal variables, and then do the actual move/resize after a timer. No flicker, no new messages.