From mint-bounce@lists.fishpool.fi Mon Apr 17 22:35:42 2006 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de X-Envelope-From: Gerhard_Stoll@b.maus.de X-Envelope-To: From: Gerhard_Stoll@b.maus.de (Gerhard Stoll) To: mint@fishpool.com Subject: [MiNT] wind_set(WF_TOPMOST) extension Message-ID: <200604172017.p46481@b.maus.de> In-Reply-To: <1145293368.4443ca38d6ec4@webmail2.utbm.fr> Date: Mon, 17 Apr 2006 20:17:00 +0200 Organization: MAUS Berlin (+49-30-82701142) X-Gateway: b3.maus.de gb1.1r 102698.1858 X-Gateway-Administrator: postmaster@b3.maus.de Lines: 23 X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-To: mint-bounce@lists.fishpool.fi X-original-sender: Gerhard_Stoll@b.maus.de Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: 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.9 tagged_above=-50.5 required=7.0 tests=AWL, BAYES_00 X-Spam-Level: > no new API in MyAeS that it is not in XAAES so XaAES do not supported Interface Resource File Format. I know that is document in the gemlib. > (except two extension of wind_set(230 and 231) not very important that > I use internaly and should probably document one day). Ony day that can be to late if someone use this number too. It is not important what this modes do, but that you use that mode is good to know. > I think easier, is to do this test with an id window like -2 Sorry, I don't real understand what is easier if I wrote wind_set(-2,WF_TOPMOST) instead of use appl_getinfo. I agree with Odd that you break the rule to get info about the AES, without using app_getinfo. > and how do you do with wind_set()? In the same way like wind_get. Gerhard