Sun 19 Oct 2008 09:01:31 PM UTC, comment #9:
Thanks for your efforts. It's better than ever and OK to close.
However, it seems you had to trick a little bit and that groups are not represented like they should:
[{1}][${2,3,4}][{5,6,7}] // movement
[{1}][][${2,3,4},{5,6,7}] // deselection (via button); selection
[${1}][][{2,3,4},{5,6,7}] // movement
[][][${1},{2,3,4???5,6,7}] // movement
[${1}][][{2,3,4,5,6,7}][] // notice, the groups were joined
Legend:
[] -- tile
{} -- group
$ -- focus
1-7 -- a unit with id 1-7
??? -- not observable
I suspect, the groups are joined because they are shown in the GUI as [${1},{2,3,4,5,6,7}]. This should not be necessary, but I can live with it.
|
Sat 18 Oct 2008 07:53:10 AM UTC, comment #7:
Looks like a mess to me. That said, I'm not familiar with C++ or C code, so I can't help you there. Unless of course, you interpret the code for me and give me an understanding what kind of data structure this is.
What I would like to represent a single tile is a List of Stacks (a Stack being a special kind of List). Then no automatic grouping or ungrouping should be necessary at all.
|
Fri 17 Oct 2008 03:20:08 PM UTC, comment #2:
It seems that the game can only handle a single "two stacks on a tile", without decombining the stacks.
Legend:
[] -- Tile
{} -- Stack group
$ -- Focus
1-7 -- units
[${1,2,3}][{4,5}][{6,7}] // movement
[][${1,2,3},{4,5}][{6,7}] // deselection (via button)
[][{1,2,3},{4,5}][{6,7}] // re-selection
[][${1,2,3},{4,5}] // notice: stack info is preserved
[${1,2,3}][{4,5}][{6,7}] // movement
[][${1,2,3},{4,5}][{6,7}] // selection
[][{1,2,3},{4,5}][${6,7}] // re-selection
[][${1},{2},{3},{4},{5}] // notice: stack info is lost
|
Fri 17 Oct 2008 11:58:36 AM UTC, comment #1:
I think you meant to say that the grouping information is not loaded or saved. This should be fixed.
You have noticed that stack groupings do not work exactly like warlords yet. It is a very tricky behaviour to get right.
Here's another case that doesn't work:
1. take a stack of 3 army units and move one army units out of it.
2. group the remaining 2 army units and move them on top of the single army unit
notice that the stacks merge, but the two army units I had grouped in the incoming stack are no longer pre-selected.
I find your test case hard to follow. Can you restate it with a numbered list?
|
Fri 17 Oct 2008 10:53:10 AM UTC, original submission:
If you move a stack onto another, deselect it and reselect it, the stack remains grouped.
If you deselect a stack "S", select some other stack, deselect that and reselect the original stack "S", it is decombined (just the first unit is selected).
Also information about stacks are not loaded or saved.
Is this behavior dictated by the current data structures?
|