From mint-bounce@lists.fishpool.fi Thu Dec 8 22:32:56 2005 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de Subject: Re: [MiNT] WM_REPOSED implementation From: Odd Skancke To: MiNT List In-Reply-To: <43988E5F.6000201@free.fr> References: <4397F4C3.7030701@utbm.fr> <1134035229.5776.50.camel@linuxbox> <4398098F.2010604@utbm.fr> <43988E5F.6000201@free.fr> Content-Type: text/plain Date: Thu, 08 Dec 2005 22:28:35 +0100 Message-Id: <1134077315.29437.27.camel@linuxbox> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-7) Content-Transfer-Encoding: 7bit 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: 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=1.3 tagged_above=-50.5 required=7.0 tests=AWL, BAYES_00, RCVD_IN_SORBS X-Spam-Level: * Hi Arnaud, tor, 08,.12.2005 kl. 20.49 +0100, skrev Arnaud BERCEGEAY: < big snip > > BTW, wind_xxx() is not so bad, but i don't like the support of that > feature per window basis. Did you read my other posting where I give reasons to try and keep things collected? I know that this particular message, WM_REPOSED, isnt a good example here. But I still feel that wind_set(WF_OPTS) is the right place. Either you know about wind_set(WF_OPTS) and thus knows about WM_REPOSED (and other settings you may want to change for windows) and then do an initial wind_set(WF_OPTS, -1, ...) to set your 'generic' window options, or you dont. Since these two things are of the same age, you may say that WF_REPOSED and wind_set(WF_OPTS) go together. Splitting up and having more than one function deal with the same thing is not good I think. I would opt to keep things classified as 'window options' configurable via the obvious call, in this case wind_set() Best Regards, Odd Skancke