Vassal 3.2.8 lost library - Mac

Technical Support & Bugs
21

Thus spake jtbmap:

Got it - thanks. I located the file in the Finder and tried to restore
the oldest version I have on my backup drive. Unfortunately, the
library still comes up empty. It looks like I’m out of luck but are
there any other options to restore?

Recall that I requested above to see that file. That was why I asked you
to look for it. Since you now have more than one verison of the file
floating around, please state which version of the file you’re posting,
or better, post both.

–
J.

22

John, I have to apologize for my response to you a few days ago. You were 100% correct–the command as supplied by bugggg indeed doesn’t work. It would have had to look like this to work: ls -l ~/Library/Application\ Support/VASSAL

23

Here are the two V_global files - the current version and the oldest I can recover (November 18). If I substitute the new file and launch Vassal, the file appears to “revert” to the newer version.

24

Did that upload anything? I used the full editor to upload the files, but I don’t see anything showing up.

25

No problem - not knowing Unix, I moved the quotation marks:

ls -l ~/Library/“Application Support”/VASSAL

and that seemed to work as well.

26

Thus spake jtbmap:

Did that upload anything? I used the full editor to upload the files,
but I don’t see anything showing up.

No, nothing was uploaded.

–
J.

27

It tells me that the extension is not allowed, although the files don’t have any (visible) extension.

28

Thus spake jtbmap:

It tells me that the extension is not allowed, although the files don’t
have any (visible) extension.

Try zipping them.

–
J.

29

Thanks - this should do it

[attachment=1]V_Global.zip[/attachment]

[attachment=0]V_Global (Nov 18).zip[/attachment]

30

Thus spake jtbmap:

Thanks - this should do it

Neither of these have the files in your module library listed in them,
so I can’t help you recover that using them.

The bug which affected you was Bug 10641, which we’ve fixed as of
3.2.9-svn9843. I would suggest you use the curent 3.2.9 dev build, but
unfortunately, the 3.2.9 dev builds don’t run on some Macs, which is a
problem we’re investigating presently. Once we have that solved, we’ll
release 3.2.9, so you shouldn’t have any further problems with your
module library after that.

–
J.

31

Thanks. I did have trouble with 3.2.9-svn9843, but haven’t investigated further. I’ll wait for the release of 3.2.9 before rebuilding the module library.

32

Thus spake jtbmap:

Thanks. I did have trouble with 3.2.9-svn9843, but haven’t investigated
further. I’ll wait for the release of 3.2.9 before rebuilding the
module library.

We believe we’ve corrected the preferences writing problem you were
seeing as of 3.2.9-svn8955, which you can find here:

vassalengine.sourceforge.net/builds/

Waiting to rebuld the module library until 3.2.9 is released is the
wrong way around—we’d like to have confirmation from people who were
having this problem that they no longer experience it before we release
3.2.9.

J.