VASSAL 3.4.8 Released

[uckelman]

VASSAL 3.4.8 Released

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

Release notes: http://www.vassalengine.org/wiki/VASSAL_3.4_Release_Notes

Changes since 3.4.7:

Bug fixes

• 13577: Stacks properly restore their visual 'layer' level when saved/restored
• 13574: Fix reporting on oldXXXXXX properties in ReportState
• 13573: Beanshell count function not working with $$ variables in Restrict Commands property match
• 13567: Put backup in better location when writing to module fails and ensure Editor is not left in a bad state
• 13560: Don't register mouse listeners from ActionButton.draw()
• 13449: Inventory window remains open when the game is closed in the Player
• 13379: Mass Piece Loader - Decrease key now loads correctly
• 13379: Mass Piece Loader - Layers are no longer loaded Activated

Other improvements

• 13572: Stop converting preferences last written by 3.2.7 or earlier
• 13563: Hitting Enter in Editor expands or edits nodes
• 13431: Cache grid and grid numbering painting for better performance
• 13379: Mass Piece Loader - Base Image can now be loaded into layers
• 10063: Hitting Enter on Module Manager opens the module

 

[Rindis]

I'm getting this upon loading VASL 6.6.1 in this version:

- [Out Of Date Custom Code] This module contains outdated custom code, which is not guaranteed to work with versions of VASSAL released after 6-Aug-2021.
- [Out Of Date Custom Code] Please check whether there is an updated version of this module. If not, please contact the maintainer of this module and request that it be fixed, or post a message on the Vassal forums and ask for help

No immediate problems, but still seeing the warning.

 

[uckelman]

I'm getting this upon loading VASL 6.6.1 in this version:

• [Out Of Date Custom Code] This module contains outdated custom code, which is not guaranteed to work with versions of VASSAL released after 6-Aug-2021.
• [Out Of Date Custom Code] Please check whether there is an updated version of this module. If not, please contact the maintainer of this module and request that it be fixed, or post a message on the Vassal forums and ask for help

No immediate problems, but still seeing the warning.

That's the expected behavior, because VASL 6.6.1 is using deprecated methods which will be removed from VASSAL next summer. There's already work underway to update VASL.

 

[von Marwitz]

The question came up if it is somehow possible for Windows and dividing bars within windows to 'remember' their position. Bruce mentioned here that he was once told some VASSAL limitation prevented this, see here.

As we have seen quite some work going on on VASSAL, maybe it is possible to fix this now, so I thought I just might bring it to attention to @uckelman here.

In case this is a VASL issue, I will crosspost there, too.

von Marwitz

 

[uckelman]

Is there a ticket in our tracker for this?