Vassal 3.6.1 Released

[uckelman]

VASSAL 3.6.1 Released

Download: https://github.com/vassalengine/vassal/releases/tag/3.6.1

Release notes: https://vassalengine.org/wiki/VASSAL_3.6_Release_Notes

Changes since 3.6.0

New features

* 10879: Dice Button raw result and counts reporting

Bug fixes

• 10876: Remove unwanted nulls from Inventory
• 10871: Display proper name for Set Global Property and Place Marker in Editor
• 10869: Inventory shouldn't show pictures/text for pieces in private windows not currently accessible
• 10861: Polygon read from coordinates list should never be null

Other improvements

* 10880: Create HintTextFields lazily

 

[Stewart]

* 10879: Dice Button raw result and counts reporting

This is a new feature?
How is it different new from before?
Does this mean to include specific occurrences of DR per category?

I don't notice anything new

 

[uckelman]

$rawRolls$, $rawCount#$, and $count#$ are new properties which can be referenced in the DiceButton report format. You wouldn't see any change unless you edited a module to use them. The details are in the section of the reference manual for DiceButton.

BTW, I'm still waiting for a test case for your undo problem.

 

[Stewart]

$rawRolls$, $rawCount#$, and $count#$ are new properties which can be referenced in the DiceButton report format. You wouldn't see any change unless you edited a module to use them. The details are in the section of the reference manual for DiceButton.

BTW, I'm still waiting for a test case for your undo problem.

I sent the file minutes after you requested it.
As you step through the log it shows undoing the steps and it jumping around.

 

[uckelman]

I sent the file minutes after you requested it.
As you step through the log it shows undoing the steps and it jumping around.

That's not what I asked for, and I said so in my reply at the time.

I need steps for reproducing the problem, not a log. A log preserves the commands produced by the actions you took. Having the list of commands is not the same thing as knowing what the actions were that produced the commands, and a divergence between the commands recorded and the actions producing the commands is exactly what's at stake here.

I also doubt that log is a minimal example. Does it really take dozens of moves to trigger the problem? That's rarely so. You could spend some time finding a minimal test case, or demonstrating that there's not one if there's not.

 

[Stewart]

Steps..

1. Put units on map.
2. Start Log File.
3. Name log file and store in convenient location.
4. move units around the map using ANY means available in VASL.
5. Do this for a series of about 5-6 units moving 5-6 hexes.
6. Save Log.
7. Load Log.
8. Step through log about 15+ times.
9. Press the UNDO button until you see the error.

Error occurs typically about the 6th key stroke of UNDO. The Faster you click it the sooner it seems to screw up.

The ONLY commands used in this bug are Moving units, saving files, loading files, Step through log, UNDO last move.

That's all ... Its not the 5th button every time...but you can't UNDO for more than a short number of moves.

 

[uckelman]

I can't reproduce the problem from those steps. Can you pare this down to steps where I don't have to make any choices to trigger the problem?

E.g., how many units do you need on the map? Can you trigger the problem with only one?