VASSAL 3.5.0-beta2 Released

[uckelman]

VASSAL 3.5.0-beta2 Released

Download: https://github.com/vassalengine/vassal/releases/tag/3.5.0-beta2

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

Changes since 3.5.0-beta1:

Bug fixes

• 13825: "Module from older version" check is too strict
• 13823: Map/Module Global Key Command Description not being saved
• 13821: SendToLocation does not create Movement Trail points
• 13783: Non-rectangular trait should remember name of image that created it
• 13782: Suffix/Prefix fields in Layer trait are not displayed correctly
• 13781: Bad parameter in Editor.UniqueIdManager.more_than_one message
• 13771: NPE after cutting/pasting piece palettes in Editor
• 13755: Chess clock help file is misnamed
• 4324: Antialiasing RenderingHints not set properly for drawing game components

Other improvements

• 13813: Simplified communication between Module Manager, Player, Editor
• 13792: Combined save and log loading; Load Continuation moved from File to Tools menu
• 13777: Improved workflow of zone editor
• 13761: Refer to MacOS instead of MacOS X now that MacOS 11 is out

Changes since 3.4.12:

New features

• 13706: Console, for entering commands to affect errorlog, properties, etc.
• 13522: Performance improvements for Global Key Commands
• 13504: Simpler way to display PDF files from Help menu
• 13494: Expose version numbers and module strings to module as properties
• 13432: MouseOverStackViewer can show > 1 piece of a deck
• 13417: Editor's search function can now search piece traits and component attributes
• 13415: MouseoverStackViewer has HTML support and additional formatting options
• 13414: "Help" button (and help information) added to Preferences dialog
• 13368: Added preference to control drag-at-edge-of-map width
• 13355: Threshold for centering on opponent's move is now configurable
• 13352: Title Bar of module should always show most recent Save/Load/Log
• 13297: Ability to Deselect a piece with a Key Command (also remove it from its stack)
• 13296: Flare feature for map
• 13219: Added KeyNamer for overriding key names
• 1868: Method for removing unused images from modules
• 1826: Aesthetic improvements to dialogs
• 1807: Chess clocks
• 1804: Added Preference for turning off sounds

Bug fixes

• 13741: DataArchive.getImageNames() incorrectly returns an empty string if images/ has an entry in the ZIP archive
• 13675: Piece Slots shouldn't be allowed at very top level of Piece Palette
• 13660: Replaced ComponentSplitter with SplitPane for better splitter positioning
• 13659: "Remember window size" preference is no longer ignored
• 13593: Global preferences are written when changed
• 13509: Save As in Editor, if it fails, complains the new filename
• 13495: Wizard should set the initial value for next save/load dialog
• 13336: Fixed incorrect date format in SecretNotesController
• 12946: Prevent top level required components from being deleted in Editor
• 4779: Comparison operator >= no longer incorrectly documented as =>

Other improvements

• 13661: Simplified ZIP archive writing and error reporting
• 13450: Improve look of Auto Configured editor dialogs
• 13437: Improve visibility of Logging status - Help people to remember to start logs
• 13363: buildFile renamed to buildFile.xml
• 13354: Add a chatter message when starting to write a logfile
• 13353: Use native file chooser on Linux
• 13333: Better handling of logfile/savefile comments
• 13326: Saving a module will default to .vmod, an extension to .vext
• 13323: Player switching sides now reported in Chat Log
• 13098: Move Compatibility related preferences on the General tab to a new Compatibility tab
• 1907: Suggest default filename extensions

 

[hongkongwargamer]

Just installed and clicked to run VASL 6.6.1

 

[uckelman]

Looks like VASL will need a small modification for 3.5.0 or we'll have to backport a change in the image tiler to 3.4. That's useful information. Thanks for testing.

 

[uckelman]

Try the VASSAL-3.5.0-SNAPSHOT-dep_tilinghandler_vasl-83a664505 build, available here. Does that solve the problem for you?

 

[hongkongwargamer]

Try the VASSAL-3.5.0-SNAPSHOT-dep_tilinghandler_vasl-83a664505 build, available here. Does that solve the problem for you?

Hm .. thx but not quite ..

 

[uckelman]

Are you certain you were running the test build I mentioned above? I cannot replicate the problem with the test build.

Maybe you could post the errorLog which the last run produced?

 

[hongkongwargamer]

Are you certain you were running the test build I mentioned above? I cannot replicate the problem with the test build.

Maybe you could post the errorLog which the last run produced?

Yes I am certain. What's an errorLog and where would I find that?

 

[uckelman]

That screenshot doesn't demonstrate that you were running the correct version. Instructions for finding the errorLog are here.

I missed reinstating one of the members which VASL uses that was removed after 3.5.0-beta1, and didn't catch it because the board I selected as a test was already in my tile cache from a previous run. Try VASSAL-3.5.0-SNAPSHOT-dep_tilinghandler_vasl-7a7ea4d56 instead, which you can download from the same place.

 

[hongkongwargamer]

That screenshot doesn't demonstrate that you were running the correct version. Instructions for finding the errorLog are here.

I missed reinstating one of the members which VASL uses that was removed after 3.5.0-beta1, and didn't catch it because the board I selected as a test was already in my tile cache from a previous run. Try VASSAL-3.5.0-SNAPSHOT-dep_tilinghandler_vasl-7a7ea4d56 instead, which you can download from the same place.

I can only run the version as you tell me to run. I just ran the version again as per what you stated above and got the same error.

 

[hongkongwargamer]

That screenshot doesn't demonstrate that you were running the correct version. Instructions for finding the errorLog are here.

I missed reinstating one of the members which VASL uses that was removed after 3.5.0-beta1, and didn't catch it because the board I selected as a test was already in my tile cache from a previous run. Try VASSAL-3.5.0-SNAPSHOT-dep_tilinghandler_vasl-7a7ea4d56 instead, which you can download from the same place.

I don't have a folder call "VASSAL" under "Application Support". Sorry.

 

[uckelman]

Ok, then I need to see the errorLog from the last run in order to proceed. Try searching your filesystem for a file with a name starting with "errorLog". I will be interested to know where it turns up, and what version of Mac OS you're running.

 

[hongkongwargamer]

Ok, then I need to see the errorLog from the last run in order to proceed. Try searching your filesystem for a file with a name starting with "errorLog". I will be interested to know where it turns up, and what version of Mac OS you're running.

7a7ea4d56 gives the same "Uncaught Exception" window.

Did a file name search on my Mac for "errorLog". The only thing I can find is from 2013 referring to VASSAL 3.0.18 / VASL 5.8.1

Sorry!

 

[uckelman]

Alternatively, you could expand the dialog to see the stack trace from the error and paste that here. That would also be helpful.

(And the errorLog is available under Help > Show Error Log in the Module Manager, even if you can't determine where it is on disk.)

 

[hongkongwargamer]

Joel - it's too long to post. I just sent you an email.

 

[zgrose]

7a7ea4d56 gives the same "Uncaught Exception" window.

Did a file name search on my Mac for "errorLog". The only thing I can find is from 2013 referring to VASSAL 3.0.18 / VASL 5.8.1

Sorry!

The path ~/Library/Application Support/VASSAL is correct in Big Sur (OS X 11.1) and pretty sure it is the same in Catalina. You may have been looking in the wrong Library folder.
The easiest way to make sure you're in the correct Library is to type that bolded path into the Go to Folder dialog (Command-Shift-G in the Finder). The VASSAL folder is where all your qconfigs and whatnots are, so you definitely have one. Note the ~ in front, that's important.

 

[hongkongwargamer]

The path ~/Library/Application Support/VASSAL is correct in Big Sur (OS X 11.1) and pretty sure it is the same in Catalina. You may have been looking in the wrong Library folder.
The easiest way to make sure you're in the correct Library is to type that bolded path into the Go to Folder dialog (Command-Shift-G in the Finder). The VASSAL folder is where all your qconfigs and whatnots are, so you definitely have one. Note the ~ in front, that's important.

Thanks! Just sent 3 errorLogs to Joel via email .. and added an alias for the folder on my Desktop for next time.

 

[uckelman]

You were hitting two problems---the one I fixed, and another due to a change which affects a die roller extension you're loading. We'll get you a test build addressing the other problem soon.

 

[uckelman]

Try VASSAL-3.5.0-SNAPSHOT-d334a25aa, available the same place.

 

[hongkongwargamer]

Try VASSAL-3.5.0-SNAPSHOT-d334a25aa, available the same place.

It runs! Thx.
Which dice roller extension is getting messed with?

 

[uckelman]

It runs! Thx.

Great. Thanks for testing.

Which dice roller extension is getting messed with?

I'd have to look back at your errorLog to see which one was being loaded; the issue wasn't caused by the extension itself, but was only uncovered by it because it used a class of ours which isn't run normally.