From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10094 invoked by alias); 23 Sep 2003 16:29:09 -0000 Mailing-List: contact xconq7-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: xconq7-owner@sources.redhat.com Received: (qmail 10087 invoked from network); 23 Sep 2003 16:29:08 -0000 Received: from unknown (HELO smtp2.fre.skanova.net) (195.67.227.95) by sources.redhat.com with SMTP; 23 Sep 2003 16:29:08 -0000 Received: from [212.181.162.155] (h155n1fls24o1048.bredband.comhem.se [212.181.162.155]) by smtp2.fre.skanova.net (8.12.10/8.12.10) with ESMTP id h8NGT3bq024313; Tue, 23 Sep 2003 18:29:04 +0200 (CEST) X-Sender: u22611592@m1.226.telia.com Message-Id: In-Reply-To: References: <3F705D18.8040005@xwt.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 23 Sep 2003 19:14:00 -0000 To: Eric McDonald From: Hans Ronne Subject: Re: 7.5 release? - How you can help Cc: xconq7@sources.redhat.com X-SW-Source: 2003/txt/msg00445.txt.bz2 >P.S. I guess I'll have to make sure the Web site says >"approaching" (which I thought it did) rather than "imminent". Or rather, I should abstain from optimistic forecasts on this list :-). Other things to do before a release: 1. Fix the recently discussed font problems in the tcltk interface (almost done). 2. Add several new game modules and update all the existing ones (ditto). 3. Fix the memory problems on Windows. This is the big one. Several game modules crash under Windows 98, probably due to the limit on the GDI resource memory. In fact, after I updated the game modules, adding some more images to imf.dir, every single game crashes under Windows 98 (this is one reason why I haven't checked in these updates yet). I don't think it is acceptable for a release version of Xconq to crash with 100% certainty on what is still one of the biggest installed platforms worldwide, even if it works fine everywhere else. However, I'm not sure what to do about it. I guess we could rewrite the imaging code so that it uses less memory, possibly fix some leaks, but this is quite some work. And it would probably only fix things until the next game module update adds even more images. I would therefore be very interested to hear if there are any known shortcuts or hacks to deal with the GDI resource problem. It is after all a well-known limitation in Windows 98 that many programmers must have stumbled on before. Any suggestions are welcome. Hans