From mint-bounce@lists.fishpool.fi Sun Apr 30 22:54:16 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: <1146415707.4454ea5b874cc@webmail2.utbm.fr> References: <200604171528.p46480@b.maus.de> <1145293368.4443ca38d6ec4@webmail2.utbm.fr> <1146334431.5682.94.camel@linuxbox> <1146380727.445461b7b0355@webmail1.utbm.fr> <1146413337.5682.101.camel@linuxbox> <1146415707.4454ea5b874cc@webmail2.utbm.fr> Content-Type: text/plain; charset=UTF-8 Date: Sun, 30 Apr 2006 22:40:28 +0200 Message-Id: <1146429628.5682.118.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 k3UKsG0p003495 søn, 30,.04.2006 kl. 18.48 +0200, skrev olivier.landemarre@utbm.fr: > Quoting Odd Skancke : > > > 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 :) > > If you send me directly xaaes binary, I try to test it. I can send you a binary, ofcourse. If you already have an XaAES installation, what do you have installed? > > I have just to see a bug for this part in myaes unfortunatly :-( Oh.. <-snip-> > > > > > > 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? > No absolutly no because I have not put any documentation for this, this is add > only in first time for internal use, and as I think it could be usefull, I just > put it. > > #define WF_USER_POINTER 230 > > long is pass in wind_set() with p1 and p2 > > wind_get() return value in intout[1] and intout[2] > > > > > > 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? > Yes of course for a very long time (since hierarchical menu are implemented > because I use it internaly for this) Hmm... isnt it dangerous to use it internally while it is accessible 'from the outside'? Isnt it harder to maintain this? > > What is the function name, if any? > > #define WF_WIND_ATTACH 231 > > in p1 there is the number of the window to attach to the target window design > > wind_get() return in intout[1] if there is the window attach > and in intout[2] if target window is itself an attach window the window on wich > it is attach, 0 of course for a standard window This attachment, is it related to the open/closed status of the parent window? I mean, the window(s) attached this way will be slaves of the parent window when closing/opening(), right? Incase this is to be extended later, perhaps it would be a good idea to indicate what kind of attachment one wants by selecting this; wind_set(handle, WF_WIND_ATTACH, phandle,type,0,0) where handle is the handle of the window to attach to phandle, and type is bitmask indicating attach-links, For example OPEN(1), FOCUS(2), etc. Just an idea. Best Regards, Odd Skancke