Re: [Triplea-develop] Some bug fixes

[Sean B. <sbr...@ya...>]

Its good to hear your back.


> I will keep working on these game play bugs. Next up
> is allowing users 
> to choose where battleships bombard if at all (my
> current thinking is 
> between the combat move and combat phases to cycle
> through each 
> battleship adjacent to a battle and query the user
> if it should bombard 
> and where)

I think it will be ok to do it in combat phase.  When
the user selects a battle, you can pop up a dialog
asking him if the batteship in territory X should
bombard.  If there are more than one battleships a pop
up will come up asking how many (if the battleships
have different movement values you can either split
the battle ships up by movement, or simply take the
battleships with the lowest movement first).  In the
rare case that there are two adjacent territories with
battleships then it should be ok to pop up two
different dialoges.  

> 
> One general organization note is that I think it
> would be a good idea to 
> tag the codebase for each release (using cvs tag).
> This will allow us to 
> easily revert to a release version to check out bugs
> and figure out the 
> differences between releases.
> 

That is a good idea.  Nekro, can you do that with the
next release.

> By the way does anyone know where the code that
> loads the last saved 
> game and can cause the unsightly exception when
> TripleA loads? I can't 
> only find the code that loads the last game type
> (classic, 4th edition, 
> etc.).
> 

I think fixed that bug in cvs before I left.

Sean