RE: Xconq testing: Win2K

[Hans Ronne <hronne at comhem dot se>]

>>>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