From mint-bounce@lists.fishpool.fi Wed Jul 13 21:47:14 2005 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de Subject: Re: [MiNT] WCOWORK operating mode From: Odd Skancke To: MiNT List In-Reply-To: <1121282010.9341.5.camel@joy.home> References: <1121282010.9341.5.camel@joy.home> Content-Type: text/plain; charset=utf-8 Date: Wed, 13 Jul 2005 19:43:18 +0000 Message-Id: <1121283798.29088.119.camel@linuxbox> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-4) 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=-0.8 tagged_above=-50.5 required=7.0 tests=AWL, 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 j6DJlEFM003806 ons, 13,.07.2005 kl. 21.13 +0200, skrev Petr Stehlik: > 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. And I have said, numerous times, it is the AES's responsibility to make sure the app gets correct data. So, you are wrong. Best regards Odd Skancke