From mint-bounce@lists.fishpool.fi Tue Apr 18 08:34:59 2006 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de Message-ID: <444488A8.4070300@utbm.fr> Date: Tue, 18 Apr 2006 08:35:20 +0200 From: Olivier Landemarre User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Gerhard Stoll Cc: mint@fishpool.com Subject: Re: [MiNT] wind_set(WF_TOPMOST) extension References: <200604172017.p46481@b.maus.de> In-Reply-To: <200604172017.p46481@b.maus.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-To: mint-bounce@lists.fishpool.fi X-original-sender: olivier.landemarre@utbm.fr 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.6 tagged_above=-50.5 required=7.0 tests=AWL, BAYES_00 X-Spam-Level: Gerhard Stoll wrote: >>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. > > Oh yes I forget this! > > >>(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 have already send new feature to Arnaud in the past for gemlib, he not put it, probably I should write it somewhere. >>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. > > > Yes of course, but really this is not the best, we can do I think, this is quite complicated, I think. Of course we could put it in appl_getinfo() if you prefer, this was just a proposition. >>and how do you do with wind_set()? >> >> > >In the same way like wind_get. > > > Ok so I have to test this, it looks strange for me. Olivier >Gerhard > > > > > >