From mint-bounce@lists.fishpool.fi Fri Apr 14 14:51:41 2006 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de Message-ID: <1145018821.443f99c511bdb@imp5-g19.free.fr> Date: Fri, 14 Apr 2006 14:47:01 +0200 From: arnaud.bercegeay@free.fr To: MiNT List Subject: Re: [MiNT] wind_set(WF_TOPMOST) References: <443E1915.5090804@utbm.fr> <443E9A2B.6680.17817B8@localhost> <1144969895.25823.119.camel@linuxbox> <1144998269.443f497de58c5@webmail1.utbm.fr> <1144999862.25823.150.camel@linuxbox> <1145007472.443f6d70304a3@imp3-g19.free.fr> <1145010821.2 In-Reply-To: <1145010821.25823.172.camel@linuxbox> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 User-Agent: Internet Messaging Program (IMP) 3.2.5 X-Originating-IP: 57.67.17.100 X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-To: mint-bounce@lists.fishpool.fi X-original-sender: arnaud.bercegeay@free.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=4.3 tagged_above=-50.5 required=7.0 tests=BAYES_00, NO_REAL_NAME, 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 k3ECpeLu025220 Hello, > I agree. Not very good to have that kind of thing. Therefore TOPMOST > should be used by system-apps only. I don't understand very well *why* this should be reserved to system-apps. If i don't like an application look'n feel, i just don't use it. I don't want the AES to forbid this application for me. Let's take the example of an application that uses its own widget rendering in place of the AES rendering (EZEdit for example). If i want a text editor to have windows with real AES widget, i just chose another editor. I understand that you may prefer to limit the usage of TOPMOST windows to system-apps only on your setup, but then you just have to NOT install standard app that uses TOPMOST windows... Is there any security reason (?) to limit the usage of TOPMOST windows to system-apps ? Or is it just a preference (and then, no really reason to impose that choice to everyone). Don't get me wrong, i just want to understand the motivation of that choice. I don't say it's a bad choice. > Here I do not agree. I think the examples I've seen so far belong to > the 'alert' group of windows, or situations where the user would choose > it to be TOPMOST. ... and to be without BUTTON, and to have a total control of the rendering (not only a string + icon), and to change the rendering of the "alert" from time to time (evolution in real time of the message by alert_draw() ?), and to close the "alert" when it is no more usefull (alert_close() ?)... well this is exactly the definition of a window set on TOPMOST without focus, i mean the initial proposal of Olivier. > Besides, I dont agree that TOPMOST windows never > should have focus. So we are not talking of the same thing, and it's natural that we cannot find a common solution ;) You consider the TOPMOST window as a "standard" window wich is just displayed in top of other (introduction of a 2nd layer of windows)... and in that case, i agree with most of what you post here, and i disagree with what i post here. In Olivier's idea (and what i consider useful for applications), the "topmost" layer of windows cannot give the focus to the application, and it fit very well to the usage i tried to describe. And no, this is not alert. This is a kind of "user window that contain a high priority message". For example, teatime may open a small TOPMOST window somewhere on the screen that show the countdown in real time... displayed over the QED full sized window where you are typing a text. Aniplayer may display the title of the next OGG file to be played with a small image of the the CD-cover in the TOPMOST window. A destop utility may display a "disk near full" message in a TOPMOST window, with the progression of the disk free memory in real time... and the TOPMOST window will be closed as soon as the amount of free memory on the disk is ok. No timeout to close this "alert" window. best regards, Arnaud.