From mint-bounce@lists.fishpool.fi Wed Jul 13 21:14:27 2005 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de Subject: Re: [MiNT] WCOWORK operating mode From: Petr Stehlik To: MiNT List In-Reply-To: References: Content-Type: text/plain; charset=ISO-8859-2 Date: Wed, 13 Jul 2005 21:13:30 +0200 Message-Id: <1121282010.9341.5.camel@joy.home> Mime-Version: 1.0 X-Mailer: Evolution 2.2.2 X-MIME-Autoconverted: from 8bit to quoted-printable by ms1.avonet.cz id j6DJDbnr001766 X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-To: mint-bounce@lists.fishpool.fi X-original-sender: joy@sophics.cz 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=BAYES_00 X-Spam-Level: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by wh58-508.st.uni-magdeburg.de id j6DJEQYh008829 Frank Naumann píše v St 13. 07. 2005 v 20:55 +0200: > Hello! > > > With the WCOWORK option, none of these assumption are true. If some code > > receives a WM_SIZED message, it cannot know if the data are the FULL area or > > the WORK area (because maybe another lib -- considered as the same AES > > application -- may have requested the WCOWORK mode... or not. > > I think your application have a big problem if you use a library and you > don't know what the library do ... or vice versa. It's a thing you should > definitly avoid if you design something. What is wrong with you guys that you can't read what Arnaud writes. I haven't been programming GEM applications for ages but I still understand that AES messages passing coordinates from one application to another will misbehave if both applications won't work in same WCOWORK mode. Petr