module does not reappear in library after reopening Vassal

Technical Support & Bugs
21

If you’re still having a problem with modules disappearing from the module library, please try 3.2.8-svn8790, available here:

vassalengine.sourceforge.net/builds/

This build contains some changes w/r/t how preferences are stored which might solve your problem. If you try this build, please report here if whether it solved the problem for you.

22

Here is the error message I get. using Windows Vista 64-bit:

ava.io.IOException: Unable to create directory C:\Users\Mark\AppData\Roaming\VASSAL\tmp\vassal-1911617569243711676
at org.apache.commons.io.FileUtils.forceMkdir(FileUtils.java:1488)
at VASSAL.tools.io.TempFileManager.createSessionRoot(TempFileManager.java:189)
at VASSAL.tools.io.TempFileManager.createTempFile(TempFileManager.java:220)
at VASSAL.tools.io.ZipArchive.getOutputStream(ZipArchive.java:275)
at VASSAL.tools.io.ZipArchive.getOutputStream(ZipArchive.java:247)
at VASSAL.preferences.Prefs.save(Prefs.java:220)
at VASSAL.preferences.PrefsEditor.write(PrefsEditor.java:255)
at VASSAL.preferences.Prefs.write(Prefs.java:233)
at VASSAL.preferences.GlobalPrefs.handleValueChange(GlobalPrefs.java:44)
at VASSAL.preferences.Prefs$1.propertyChange(Prefs.java:70)
at java.beans.PropertyChangeSupport.fire(Unknown Source)
at java.beans.PropertyChangeSupport.firePropertyChange(Unknown Source)
at java.beans.PropertyChangeSupport.firePropertyChange(Unknown Source)
at VASSAL.configure.Configurer.setValue(Configurer.java:104)
at VASSAL.configure.LongConfigurer.setValue(LongConfigurer.java:65)
at VASSAL.launch.ModuleManager.(ModuleManager.java:331)
at VASSAL.launch.ModuleManager.main(ModuleManager.java:181)

23

Thus spake mda:

Here is the error message I get. using Windows Vista 64-bit:

ava.io.IOException: Unable to create directory
C:\Users\Mark\AppData\Roaming\VASSAL\tmp\vassal-1911617569243711676
at org.apache.commons.io.FileUtils.forceMkdir(FileUtils.java:1488)
at
VASSAL.tools.io.TempFileManager.createSessionRoot(TempFileManager.java:189)
at
VASSAL.tools.io.TempFileManager.createTempFile(TempFileManager.java:220)
at VASSAL.tools.io.ZipArchive.getOutputStream(ZipArchive.java:275)
at VASSAL.tools.io.ZipArchive.getOutputStream(ZipArchive.java:247)
at VASSAL.preferences.Prefs.save(Prefs.java:220)

This isn’t from 3.2.8-svn8790, which I can tell because Prefs doesn’t
use ZipArchive there.

Try 3.2.8-svn8790 and let us know whether you still have the problem
wit that.

–
J.

24

Not only does this happen to me every time i remove and open a module as i work on some for The Gamers OCS playtest kits, only the last (most current) module is the one that summarily disappears from the list of opened modules.

I was working on module A a few days ago and it would open just fine and stay in the list until i closed down the vassal engine.

Yesterday I was working on module B and it is now the cursed module. Module A is there in the list.

25

Thus spake perrya:

Not only does this happen to me every time i remove and open a module as
i work on some for The Gamers OCS playtest kits, only the last (most
current) module is the one that summarily disappears from the list of
opened modules.

I was working on module A a few days ago and it would open just fine and
stay in the list until i closed down the vassal engine.

Yesterday I was working on module B and it is now the cursed module.
Module A is there in the list.

Which version of VASSAL are you talking about here?

–
J.

26

sorry, i was using 3.2.7. i just installed 3.2.8 and need to test it for this specific bug/quirk.

27

a test of 3.2.8 shows that it fixed the problem. the most recent opened module has stayed in the list.