From mint-bounce@lists.fishpool.fi Wed Jun 22 00:34:29 2005 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de Date: Wed, 22 Jun 2005 00:30:36 +0200 From: Ingo Schmidt X-Mailer: The Bat! (v3.5) Professional Reply-To: Ingo Schmidt X-Priority: 3 (Normal) Message-ID: <1308273701.20050622003036@der-ingo.de> To: MiNT-Liste Subject: [MiNT] Re[2]: XAAES slow? In-Reply-To: <1119389933.15790.180.camel@linuxbox> References: <42B09A61.9020204@yahoo.fr> <1118887948.12057.11.camel@linuxbox> <42B18304.3030406@yahoo.fr> <1118934446.15790.7.camel@linuxbox> <42B1AEE7.3010707@yahoo.fr> <1119105225.15790.70.camel@linuxbox> <20050619015454.t7xyf5g6awisk0o4@coolrunningconcepts.com> <1119177626.15790.88.camel@linuxbox> <42B6B87A.1080108@seznam.cz> <1119298313.15790.119.camel@linuxbox> <42B75568.3000709@seznam.cz> <1119340933.15790.149.camel@linuxbox> <42B850F7.7030503@seznam.cz> <1119384685.15790.177.camel@linuxbox> <1119388246.42b8825611b1f@imp4-q.free.fr> <1119389933.15790.180.camel@linuxbox> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Provags-ID: kundenserver.de abuse@kundenserver.de login:58e864169f3ef71bae3e2b831e61e1a6 X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-To: mint-bounce@lists.fishpool.fi X-original-sender: ich@der-ingo.de 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.0 tagged_above=-50.5 required=7.0 tests=BAYES_00 X-Spam-Level: Hi everyone! > I cant believe this. wind_calc() does NOT work on a given window > goddamned it! It has not window context. wind_get/set() does! What the > hell is the problem with you all? I'm about to give up this shit! Plaese calm down :-) Even though you are right. And here is why you are right: The binding of wind_calc has no input parameter for w_handle. From that we can see that it was never designed to work on a "per window" basis. So wind_calc CAN NOT give you any information about a given window. Even though if it wanted to! It simply doesn't know which window we are talking about! (Imagine different themes for windows of the same app! Then wind_calc would even be totally WRONG!) So actually an app could do this: Make all the wind_calc's for all possible windows, store those values and be set. Now what happens if we have a window manager that has themes? Well, in that case there has to be another way of informing an app about a theme change. And once the app received this info, it can do all the wind_calcs again. I hope I could clarify the situation a bit! Cheers, Ingo =;->