From mint-bounce@lists.fishpool.fi Sun Apr 30 23:42:55 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: <1146431040.44552640f046a@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> <1146429628.5682.118.camel@linuxbox> <1146431040.44552640f046a@webmail2.utbm.fr> Content-Type: text/plain; charset=utf-8 Date: Sun, 30 Apr 2006 23:35:08 +0200 Message-Id: <1146432908.5682.132.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 k3ULgti0023795 søn, 30,.04.2006 kl. 23.04 +0200, skrev olivier.landemarre@utbm.fr: > Quoting Odd Skancke : > > > 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? > > yes on Aranym, I suppose I can replace an old one with a new one. How old installation do you have? Just so that I know what I have to send. > > > > > > > > > I have just to see a bug for this part in myaes unfortunatly :-( > > > > Oh.. > > Now it's fix! > > I can send you if you wan't you can launch myaes from xaaes, should work (not > test for a long time) Yes, I can try :) > > > > > > 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? > No in fact I use it for internal window, like for popup or menu, this is not > client windows, client don't know it manage this windows. Ok. > > > > > > > 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. > > > In fact like it is done, it's phandle attach to windows handle, this is more > logical ;-). Ah, okie. Altho I dont agree it is more logical, since it looks more logical to; wind_set(take_this_window, ATTACH_IT_TO, this_window, mode,0,0); which is more in the spirit of the rest of wind_set(take_this_window, AND_DO_THIS,...) style. But this is perhaps just me... > For other I not understand what you would like to do with type, I suppose we can > add some specification to said for example to have relative position to the > mother window, to sty above etc... Actually it's only an attachment, I don't > know if this feature is interesting or not. Perhaps I have misunderstood. What exactly is the behaviour of a window attached to another? What relations are made via this attachment? Best Regards, Odd Skancke