From mint-bounce@lists.fishpool.fi  Tue Jul  5 18:51:11 2005
X-Original-To: fnaumann@mail.boerde.de
Delivered-To: fnaumann@mail.boerde.de
Subject: Re: [MiNT] wind_get( WF_WORKXYWH) buggy? (was: Re: usage of
	wind_calc())
From: Odd Skancke <ozk@atari.org>
To: MiNT List <mint@fishpool.com>
In-Reply-To: <42CAA2C3.9040607@seznam.cz>
References: <op.ssud38dp8yw5lr@lon92-6-82-236-205-36.fbx.proxad.net>
	 <42BB46F0.4090206@chello.nl> <1119599743.15790.284.camel@linuxbox>
	 <op.ssxmqhk88yw5lr@lon92-6-82-236-205-36.fbx.proxad.net>
	 <1119718803.15790.339.camel@linuxbox>
	 <op.ssxylfll8yw5lr@lon92-6-82-236-205-36.fbx.proxad.net>
	 <1119779027.15790.442.camel@linuxbox>
	 <op.ssztpt1e8yw5lr@lon92-6-82-236-205-36.fbx.proxad.net>
	 <1120071508.19330.55.camel@linuxbox>
	 <op.ss5hgymf8yw5lr@lon92-6-82-236-205-36.fbx.proxad.net>
	 <1120086064.11804.57.camel@taro.coolrunningconcepts.com>
	 <op.steotny28yw5lr@lon92-6-82-236-205-36.fbx.proxad.net>
	 <op.stff49wd8yw5lr@lon92-6-82-236-205-36.fbx.proxad.net>
	 <42CAA2C3.9040607@seznam.cz>
Content-Type: text/plain
Date: Tue, 05 Jul 2005 18:47:52 +0200
Message-Id: <1120582072.5673.62.camel@linuxbox>
Mime-Version: 1.0
X-Mailer: Evolution 2.0.4 (2.0.4-4) 
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: <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.7 tagged_above=-50.5 required=7.0 tests=AWL,
 BAYES_00
X-Spam-Level: 

tir, 05,.07.2005 kl. 11.09 -0400, skrev Standa Opichal:
> Hi!
> 
> As I am back from my holidays let me jump into the discussion too. :)
> 

> Regarding the wind_calc() usage. There will be very little applications 
> that would survive on-fly theme change (cause they _use_ and will use 
> wind_calc() on and on) so this 'change theme only for new windows 
> feature' will IMHO stay experimental forever.

 As long as application/lib authors dont want to use new features, you
are right. Does this mean I should stop work on XaAES right now? It is
by now up to where n.aes is and needs no further development if this is
the attitude... I'm really getting sick of this.



 Best regards
Odd Skancke