From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29678 invoked by alias); 24 Nov 2003 02:27:41 -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 29671 invoked from network); 24 Nov 2003 02:27:40 -0000 Received: from unknown (HELO smtp10.hy.skanova.net) (195.67.199.143) by sources.redhat.com with SMTP; 24 Nov 2003 02:27:40 -0000 Received: from [212.181.162.155] (h155n1fls24o1048.bredband.comhem.se [212.181.162.155]) by smtp10.hy.skanova.net (8.12.10/8.12.10) with ESMTP id hAO2Rb96015013; Mon, 24 Nov 2003 03:27:37 +0100 (CET) X-Sender: u22611592@m1.226.comhem.se Message-Id: In-Reply-To: <000801c3b231$fdcbf650$6401a8c0@Win2k> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 25 Nov 2003 01:47:00 -0000 To: "Erik Jessen" From: Hans Ronne Subject: RE: Xconq testing: Win2K Cc: xconq7@sources.redhat.com X-SW-Source: 2003/txt/msg00916.txt.bz2 >>>Recommendations: >>1) somehow ignore the invalid terrain cleanly; new users are bound to >>mess things up, and internal errors will throw them for a loop. > >Sounds like a reasonable idea, but I'm not sure how to implement it. >Perhaps force undefined terrian to type 0 (ocean)? >-> is there any way to just not even stick it into the database when >read? Nope. Any terrain must have a defined type. That's why you get the crashes. >>I would also like to be able to strip out a specific terrain-type, in >>case I bungled the job & created an extra few early on, and would like >>to clean things up. Maybe the ability of the map-save function to not >>list any terrain for which there were no placements would do this >>perfectly? > >Not sure what you mean here. Do you want to convert one terrain type to >another automatically? That cannot be done at present. >-> no, for example let's say I created terrain-type 'village', then >didn't use any of them on the map. Or, I would like to take a 1991-Gulf >map, and use it for an 'ancients' game. I'd like all the 'airport' >hexes to convert to something else, or just disappear. Well, that's what I meant by automatic terrain conversion. A possible feature in the future, but not available now. >And even if I made a floating tcltk designer window, it would probably >keep >the focus as long as it stays in front. Meaning that you would not be >able >to edit the map. > >--> OK. How about putting the Design popup into a pane, instead? >Then it's not a popup? That might work. Perhpas one could stick it in place of the unit list. Hans