The VASSAL Team is happy to announce VASSAL 3.8.0-beta3, which is a preview release.
IMPORTANT
Saves and logs from 3.8.0-beta2 might not be openable with 3.8.0-beta3. If you have such a file and need to open it in 3.8.0-beta3, please contact us for help.
Starting with 3.7.25, Vassal requires Java 17 or newer. If you are using one of the MacOS or Windows packages, Java is bundled with Vassal and this will not affect you. If you are using Linux or another OS, please upgrade Java to at least Java 17.
Modules saved in 3.8 are not openable by earlier versions of Vassal. We recommend keeping a backup copy of any pre-3.8 modules you plan to modify in 3.8 until you’ve verified that everything works to your satisfaction.
Things may be broken which worked previously. If you find a new bug, please report it.
15141: Fix NPE when rendering boards to non-map contexts
Improvements
15121: Compress the saved-game command log with XZ
Other changes
15099: Removed the deprecated loadGameOld Action
See the Release Notes for descriptions of the changes in 3.8.
Minimum Requirements
VASSAL 3.8 requires Java 17 or later.
The Windows and MacOS packages have an appropriate version of Java bundled with them, so there is no need to install Java separately on those operating systems. On Linux, use your package manager to install Java 17 or later.
If you are using MacOS 14, please ensure you are using 14.4 or later, to avoid a bug in MacOS which prevents Vassal from starting.
Help us test
Please report bugs in the Technical Support & Bugs category at the VASSAL forum.
Standard informative Chart components - typically used to show tables or similar information - are now zoomable. A user may zoom in and out on a chart holding down the Ctrl-key and scrolling the mouse scroll wheel (or touchpad equivalent). Keyboard short cuts can be defined in the Chart.
Note to module developers: This should not make you use images with very high resolution. Zooming in to twice the native resolution on a PNG will still result in legible text.
The new component Symbolic Dice Button (animated) adds a button to the toolbar of the module. Pressing the button will, if so configured, pop up a window in which the dice roll is visualised as a short animation.
The module developer may configure the various aspects of the animation, such as
The new component is implemented on top if the existing Symbolic Dice Button, and as such has all the features of that component, including playing an audio clip, execute additional hotkey commands, and so on. Please refer to the Reference Manual for more information.
You’ve hit on one of the reasons why I wanted to eliminate Charts and make them Maps: There is no good place to put any additional UI in a Charts window.
No straightforward one. What you’re seeing there is the buttons belong to a Zoomer, which is tightly coupled to Map.
The standard way to write key combinations is with a +, not an &.
Ctrl + +, Ctrl + -, and Ctrl + 0 are standard hotkeys for zooming in, zooming out, and resetting the zoom to the default. People are likely to be familiar with them if they’ve used hotkeys in a browser in the last two decades.
This adds zoom buttons as overlays on the chart image. The buttons are normally semi-transparent, but when a user hover over it, the interface becomes more opaque. See also screenshots below
The interface could be more - if not fully : transparent. The transparency could be made configurable. Or the interface could be fully disabled via configuration. Many options.
A user can always change the size or aspect ratio of the chart window, which will often be enough to make the zoom buttons not obscure the chart. The buttons are glued to the lower left corner of the JScrollPane - not the image.
“Unusable” is an exaggeration - clearly some users have found it attractive and usable. In a any case, to meet your concerns …
I’ve updated the PR. Now, a module developer can configure various aspects for the zoom buttons put on a chart:
- The buttons can be turned completly off
The opacity of the buttons, when not hovering over them, can be set.
The width and height of each button can be set
The background and foreground colours of the buttons can be set.
I believe this provides the flexibility needed. If the buttons are a little to big for a given chart, then they can be made smaller. If they shadow important parts of the chart, then they can be made more, if not fully, transparent (less opaque), when the user isn’t hovering over them. If they do not make a whole lot of sense for a given chart, then they can be turned off altogether.