Re: Problem saving game in Win TCL, and crash

[Hans Ronne <hronne@comhem.se>]

>> However, you now need to click on the unit that you intend to attack (the
>> interface prompts "Attack  where?"). As far as I recall, this is not how
>> things worked previously.
>
>For tcltk, it has been true as long as I can remember.  At least, I
>think so.
>
>> Just putting the cursor over the enemy and typing 'a' should do the
>> trick, as Eric explained, and this is indeed how the Mac interface
>> works.
>
>Cursor as in the mouse pointer?  That seems a bit odd.  Normally the
>mouse pointer only affects mouse clicks/drags and there is a separate
>concept of "selected item" which keyboard commands act on.  I dunno,
>maybe I could get used to it.
>
>Now, moving the cursor over the enemy shows a little "attack" icon,
>which perhaps is confusing because clicking there means overrun
>rather than attack.  (or maybe it is an overrun icon....).

Well, in the Mac (native) interface the attack command works exactly like
the fire command does in both the Mac native and tcltk interfaces. Meaning
that if you position the cursor over an enemy unit, you only have to type
'a' in order to trigger an attack. No clicking on the map is required. This
is completely analogous to firing by putting the cursor over an enemy unit
and typing 'f'.

Now, the tcltk interface instead asks you "Attack where? (click to set)"
when you type 'a'. And then you have to click on the enemy unit in order to
trigger the attack. I thought that this was new behaviour, and that the
attack command used to work like the fire command (and the attack command
on the Mac). However, you are probably right. I'm not sure when I last
tested the attack command in the tcltk interface.

In any case, this raises the question if we should make both interfaces
work in the same way, and if so, how. I think the way the Mac interface
works is easier from a player point of view. It saves you one click. And
every click counts in a game like this.

Hans