From mint-bounce@lists.fishpool.fi Sun Apr 30 18:19:14 2006 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de Subject: Re: [MiNT] wind_set(WF_TOPMOST) extension From: Odd Skancke To: MiNT List In-Reply-To: <1146380727.445461b7b0355@webmail1.utbm.fr> References: <200604171528.p46480@b.maus.de> <1145293368.4443ca38d6ec4@webmail2.utbm.fr> <1146334431.5682.94.camel@linuxbox> <1146380727.445461b7b0355@webmail1.utbm.fr> Content-Type: text/plain; charset=utf-8 Date: Sun, 30 Apr 2006 18:08:57 +0200 Message-Id: <1146413337.5682.101.camel@linuxbox> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-7) 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: 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.3 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 k3UGJDNw019272 Hi, I have just checked in my first implementation of WF_TOPMOST. I think the test applications work as expected, but it would be nice to get some feedback from you who know how it should work :) Btw, thanks a lot for the test apps! søn, 30,.04.2006 kl. 09.05 +0200, skrev olivier.landemarre@utbm.fr: > Quoting Odd Skancke : > > > Hi, > > > > man, 17,.04.2006 kl. 19.02 +0200, skrev olivier.landemarre@utbm.fr: > > > Quoting Gerhard Stoll : > > > > > > > > extension to previous documentation > > > > > > > > Is there a public place where anybody can get what you have change/new in > > > > MyAES? > > > > > > Actually not, in fact there is no new API in MyAeS that it is not in XAAES > > so > > > already documented (WF_FIRSTAREAXYWH and appl_getinfo for name AES are for > > a > > > long time already put in XAAES), there is nothing more (except two > > extension of > > > wind_set(230 and 231) not very important that I use internaly and should > > > probably document one day). > > > > Would be nice to hear about 230/231 anyhow. And hopefully they will be > > available to applications; I dont think its a good idea to 'use up' > > function/mode numbering like this on internal functionality. All of the > > sudden these may get other meanings :) > > In fact this function can be usefull for application. > One is simply for add a long value link to window, there is no interact with > aes, this is for user only, for example to put pointer link to window. Ah, I see. Is this available to applications yet? And is there a name for this mode yet? > Second is to have a child window (only one at this time), when link a window to > an other window, if mother window is close, link window is close, and if this > have itself a link window of course it close etc. Sounds like a good idea actually. This is up and working in MyAES now? What is the function name, if any? Best Regards, Odd Skancke