From mint-bounce@lists.fishpool.fi Fri Apr 14 11:41:22 2006 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de Message-ID: <1145007472.443f6d70304a3@imp3-g19.free.fr> Date: Fri, 14 Apr 2006 11:37:52 +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> In-Reply-To: <1144999862.25823.150.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 k3E9fL3s007019 Hello, First, I don't think the TOPMOST feature described by Olivier needs a control by the AES (to authorise or not this feature). There is a major restriction for TOPMOST windows: they don't give the focus to the application. So, i'm sure standard applications won't use TOPMOST windows in place of standard windows. In other words, TOPMOST windows will only be used when applications really need TOPMOST windows (very particular and rare uses). Second, i don't think this is a feature related to system-application vs not-system-application. For example, the "list of task" window of a task manager may use a TOPMOST window, but other windows of a task manager (for example the "about..." window, or the "config" window) should not be a TOPMOST window. Another example: a great ;) application like teatime may use TOPMOST window. First, teatime open a standard window, here you choose your kind of tea ("green tea / 3mn" for example), and hit the "GO" button. Teatime then starts a 3mn countdown, and when the countdown reaches 0 (tea is ready), i'd like teatime to display a TOPMOST window with the message "your tea is ready" inside. This window will be automatically closed by teatime after some seconds (without any action of the user), or when the user click in this window. For that example, the TOPMOST window is the best choice, because if you are editing some text in QED for example, when teatime opens its TOPMOST window, the focus stays on QED, and you may keep typing your text without any trouble. A standard window doesn't fit to this need (QED lost the focus). A form_alert doesn't fit to this need (QED lost the focus). And as a user, i don't want the AES to ask me if teatime may open a TOPMOST window when teatime opens its TOPMOST window, because QED will lost the focus which is exactly what i don't want... and i don't want to put all the applications that may use TOPMOST windows in aes.cnf file (that doesn't make sense to put there *all* my applications). To sum up, the TOPMOST feature should not be reserved to system applications (this is not the right criteria), and i don't think we need to limit the usage of TOPMOST windows because there is a major restriction (don't give the focus) that guaranties that developpers won't use TOPMOST windows in place of standard windows. TOPMOST window are not "super" windows, it's just another kind of windows. Just my 2 cents... best regards, Arnaud.