When I open a module I’m working on, the PIECE PALETTE window is already open (it shouldn’t be).
More worryingly, when I opened up the previous module version (not edited in several days) in a previous version of vassal (3.7.16), the same thing is happening.
I’m guessing this happened because I had the Piece Pallete window open while doing testing and then closing Vassal w/ the Palette still open.
This looks like some sort of memory corruption issue. I’m going to reboot and see if this is still occurring…
Rebooting fixed it, although on relaunching Vassal, it had forgotten my user preferences (UID, password, chat log text size, etc.). So something got corrupted…
Your assertion that it “then closing Vassal w/ the Palette still open.” is exactly the reason, and it is to be expected. Vassal will - if, I believe, the option Remember main window size between sessions is enabled (Module Manager→File→Preferences) - store the state of windows and then restore the state the next time the module is loaded.
The states are stored in Vassal configuration directory/prefs/Encoded module_name, where
Vassal configuration directory depends on the platform
OS
Path
C:\Users\USERNAME\AppData\Roaming\VASSAL
~/Library/Application Support/VASSAL
~/.VASSAL
Note: On the directory C:\Users\USERNAME\AppData is typically hidden. To access that directory, write the exact path in the location bar of the File Explorer.
For example, the various preferences, options, window states of the module Battle for Moscow will be stored in
~/.VASSAL/prefs/Battle_20_for_20_Moscow
(the name is formed by first URL encoding the name, then replacing % and ; with _). These preferences files contain settings like
variable=value
and if you look through it, you will likely find the variable that says the piece palette is shown.
What makes you think that?
Rebooting is not needed. You can simply edit the preferences file, or remove it entirely to start from scratch. The user name and password (which is really the important one) are stored in the preference file as
RealName=
SecretName=
The reason why those may have disappeared is probably because you rebooted before shutting down Vassal. In that case, the preferences file may not be written correctly. The problem is not with Vassal, but rather that you rebooted the machine for no good reason.
