From mint-bounce@lists.fishpool.fi Mon May 1 11:12:00 2006 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de Message-ID: <1146474508.4455d00c98a16@webmail1.utbm.fr> Date: Mon, 1 May 2006 11:08:28 +0200 From: "olivier.landemarre@utbm.fr" To: mint@fishpool.com Subject: Re: [MiNT] wind_set(WF_TOPMOST) extension References: <200604171528.p46480@b.maus.de> <1145293368.4443ca38d6ec4@webmail2.utbm.fr> <1146334431.5682.94.camel@linuxbox> <1146380727.445461b7b0355@webmail1.utbm.fr> <1146402030.4454b4eeed83d@imp1-g19.free.fr> In-Reply-To: <1146402030.4454b4eeed83d@imp1-g19.free.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 User-Agent: Internet Messaging Program (IMP) 3.2.8 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=2.1 tagged_above=-50.5 required=7.0 tests=AWL, BAYES_00, RCVD_IN_SORBS X-Spam-Level: ** Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by wh58-508.st.uni-magdeburg.de id k419BxA4022604 Quoting arnaud.bercegeay@free.fr: > Selon "olivier.landemarre@utbm.fr" : > > > 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. > > 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. > > I'll add this in gemlib doc asap, at least to tell the world that 230 and 231 > values are already used/reserved by someone (MyAES). > > I think a bit in appl_getinfo() is usefull to complete the feature for > applications, because applications should perform some different things > depending on the availability of the feature. I wait for proposition for this, my point of view is appl_getinfo() is not definitively the best place to answer extension of wind_set() wind_get() because if we start to add new feature like this each time we add something we shoud add a flag this is not universal and quite complicated. Olivier > > Best regards, > Arnaud. > > > >