From mint-bounce@lists.fishpool.fi Wed Jun 22 01:12:12 2005 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de Message-ID: <42B89D84.6030108@chello.nl> Date: Wed, 22 Jun 2005 01:06:44 +0200 From: Henk Robbers User-Agent: Mozilla Thunderbird 1.0.2 (Macintosh/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: mint@fishpool.com Subject: Re: [MiNT] XAAES slow? 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@coolrunningco In-Reply-To: <1119389933.15790.180.camel@linuxbox> Content-Type: text/plain; charset=ISO-8859-1; format=flowed 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: h.robbers@chello.nl 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=2.1 tagged_above=-50.5 required=7.0 tests=BAYES_00, RCVD_IN_SORBS X-Spam-Level: ** Odd Skancke wrote: > tir, 21,.06.2005 kl. 23.10 +0200, skrev Xavier Joubert: > >>Selon Odd Skancke : >> >>>>But this situation doesn't happen in WinDom. The wind_calc() is used >>>>every time you do WinDom equivalent of wind_get( WORKXYWH ) so the theme >>>>change will be accomodated appropriately. >>> >>> My arguments are based on situations where theme changes does not >>>affect already created windows (which must be specifically supported by >>>each application). In this case wind_calc() will return wrong (current >>>theme) deltas instead of the (previouse theme) deltas that were >>>effective at the time the window was created. So yes, this situation >>>will arise as WinDom handles things now. >> >>This is a bug in XaAES, then. >> >>AES should always be able to compute right deltas for a given window. So you >>should either change already opened windows theme or keep old theme in memory >>to be able to handle "old" windows correctly. > > > 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! > > Odd is right. That is why wind_calc can never be cheap. I didnt want any complexity, duplication of code and future incompatabilities. So I let wind_calc create a window with the given attributes, retrieve the requested rectangle and then delete it again. Slow, but simple, and always correct. Wind_calc has very little use in general. Basically only when you know where you want the work_area. Because you must tell the border area to wind_open, you must be able to go from work_area to border area. I ever only used it for aligning the work area on a 8 pixel boundery. That was before I bought NVDI. :-) Dont use wind_calc on a already opened window. On open windows use wind_get, because the calculations need only be done when the window changes or is created/opened. -- Groeten; Regards. Henk Robbers. mailto:h.robbers@chello.nl http://members.ams.chello.nl/h.robbers/Home.html Interactive disassembler: TT-Digger; http://digger.atari.org A Home Cooked teXt editor: AHCX