From mint-bounce@lists.fishpool.fi Fri Jun 24 09:51:54 2005 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de Message-ID: <1119599276.42bbbaac63342@imp1-q.free.fr> Date: Fri, 24 Jun 2005 09:47:56 +0200 From: Xavier Joubert To: MiNT List Subject: Re: [MiNT] usage of wind_calc() References: <1119566876.15790.269.camel@linuxbox> In-Reply-To: <1119566876.15790.269.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: 212.234.144.141 X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-To: mint-bounce@lists.fishpool.fi X-original-sender: xavier.joubert@free.fr Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: 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 j5O7psN9016726 Hello Odd, Selon Odd Skancke : > What do you think? If you have other ideas, please let me know. Why not work on a per-application basis instead of a per-window basis ? I mean, apply new themes only to application supporting on-the-fly theme update (and, of course, applications opened after theme update). This would allow wind_calc() to work as expected, since you know which application is asking for it. Of course, this means keeping old themes in memory as long as an application still use it (to be able to create new windows). But I think you would have to anyway, since a theme could contains pictures or code that you wouldn't want to store in each window's structure... My 2 euro-cents, Xavier