From mint-bounce@lists.fishpool.fi  Tue Jun 21 23:26:28 2005
X-Original-To: fnaumann@mail.boerde.de
Delivered-To: fnaumann@mail.boerde.de
Message-ID: <42B8855D.80706@seznam.cz>
Date: Tue, 21 Jun 2005 17:23:41 -0400
From: Standa Opichal <opichals@seznam.cz>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
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: <42B8822F.10404@seznam.cz>
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: opichals@seznam.cz
Precedence: bulk
List-help: <mailto:ecartis@lists.fishpool.fi?Subject=help>
List-unsubscribe: <mailto:mint-request@lists.fishpool.fi?Subject=unsubscribe>
List-Id: <mint.lists.fishpool.fi>
X-List-ID: <mint.lists.fishpool.fi>
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.5 tagged_above=-50.5 required=7.0 tests=AWL,
 BAYES_00
X-Spam-Level: 

Hi!

> Hmm, what about the following:
> 
> switch( evnt_messag() )
>   case WM_SIZED:
>     give_me_work_rectangle() to optimize further redraws and setup all 
> coordinates now rather than doing this in the WM_REDRAW where this 
> doesn't belong to.
>       * for one example let say I have a lot of elements that need to 
> recompute on window size/position change and I need this to be handled 
> before I do the redraw...
> 
> Would we need an extended API to do wind_calc() in the particular window 
> context to accomodate theme changes?

Well I can always do:

mt_wind_set_grect( win, CURR, *(GRECT**)&buff[4] );
mt_wind_get_grect( win, WORK, &work );
update the work the coordinates of every element...

That would work in my case.

Can someone think of other situation that it might not work in?

So perhaps we should deprecate the WinDom's WindCalc() completely.... I 
will work on a solution of this with the WinDom guys in the mailing list 
when I get back.

Thanks again!

Standa