That’s definitely a bug! Do you know if it is logged as such yet?
No, I don’t. I’m hoping the guru of all things Vassal might know 
. I’ll see if I can do a search in the bug database and figure out if it’s there.
A thread has been posted about this on BGG:
boardgamegeek.com/thread/610709/ … o-fix-this
I tried to help, but it appears that my ideas may not have done the trick.
Thus spake pgeerkens:
That’s definitely a bug! Do you know if it is logged as such yet?
I don’t recall seeing this in the tracker. Please file a bug report for
it. (And fix it, if you want. Shouldn’t be too hard—it sounds like
someone forgot to add a WindowListener for close events to the Module
Manager.)
–
J.
I actually looked at filing an incident for this with Bugzilla, but the page
that came up looked like a truncated search page, with a Commit button.
Apparently I could add a tag to an existing bug, but there was no space for
an incident report, and no Help button.
Pieter
-----Original Message-----
From: messages-bounces@vassalengine.org
[mailto:messages-bounces@vassalengine.org] On Behalf Of Joel Uckelman
Sent: Monday, January 24, 2011 9:24 AM
To: messages@vassalengine.org
Subject: Re: [messages] [Technical Support & Bugs] Re: Module
librarydisappeared
Thus spake pgeerkens:
That’s definitely a bug! Do you know if it is logged as such yet?
I don’t recall seeing this in the tracker. Please file a bug report for
it. (And fix it, if you want. Shouldn’t be too hard—it sounds like
someone forgot to add a WindowListener for close events to the Module
Manager.)
–
J.
Thus spake pgeerkens:
I actually looked at filing an incident for this with Bugzilla, but the page
that came up looked like a truncated search page, with a Commit button.
Apparently I could add a tag to an existing bug, but there was no space for
an incident report, and no Help button.
To what URL did you go? This isn’t the way it looks for me when I file
bug reports.
–
J.
It seems that I am being take to the “Add Tag to Existing Bug” page, though
the URL definitely seems to think I am on the “Enter New Bug” page.
Pieter
-----Original Message-----
From: messages-bounces@vassalengine.org
[mailto:messages-bounces@vassalengine.org] On Behalf Of Joel Uckelman
Sent: Monday, January 24, 2011 9:36 AM
To: messages@vassalengine.org
Subject: Re: [messages] [Technical Support & Bugs] Re:
Modulelibrarydisappeared
Thus spake pgeerkens:
I actually looked at filing an incident for this with Bugzilla, but the
page
that came up looked like a truncated search page, with a Commit button.
Apparently I could add a tag to an existing bug, but there was no space
for
an incident report, and no Help button.
To what URL did you go? This isn’t the way it looks for me when I file
bug reports.
–
J.
Rindis said:
I am unable to reproduce this behaviour on Windows Vista Home Premium SP2. Can anyone verify a system on which the claimed bahaviour occurs?
I couldnt either on XP or 7. Everytime I clicked the “x” it would store my new entry changes and show them when I restarted again.
Odd. My home system has always done that. Both the old W2K system and the new W7 system.
Rindis said:
Odd. My home system has always done that. Both the old W2K system
and the new W7 system.
What version of Java are you running? I am running Version 1.6#23, and
conceivably Java has been failing to generate the proper events for this
user action.
Pieter
-----Original Message-----
From: messages-bounces@vassalengine.org
[mailto:messages-bounces@vassalengine.org] On Behalf Of Rindis
Sent: Monday, January 24, 2011 12:56 PM
To: messages@vassalengine.org
Subject: [messages] [Technical Support & Bugs] Re: Module library
disappeared
Odd. My home system has always done that. Both the old W2K system and
the new W7 system.
Read this topic online here:
https://forum.vassalengine.org/t/module-library-disappeared/3563/14
Just checked on my work system. It seems to be working fine.
So, it seems to be an individual system problem. It’s also persisted across completely separate installs of Windows. I have been transferring my entire Vassal directory (with all the subdirectories that I keep individual game modules/save files in). So, is there some file I might be dragging with me that could be causing this?
The only scenarios I can think might be happening are these:
- It was a Java bug fixed in (most likely) build 22 or 23;
- It was a VASSAL bug but that got fixed (inadvertently) in 3.1.14,
probably as part of someone’s general code clean-up. (I just now verified
that, on my system today, 3.1.14 and 3.1.15 behave the same.) - You have been neglecting to carry across the directory:
C:\Users<rindis>\VASSAL
when you moved across systems, and thus have been leaving the Module Manager
database behind, and mistakenly identified the problem with using the
Windows control box to close instead of File|Quit.
Pieter
-----Original Message-----
From: messages-bounces@vassalengine.org
[mailto:messages-bounces@vassalengine.org] On Behalf Of Rindis
Sent: Monday, January 24, 2011 1:13 PM
To: messages@vassalengine.org
Subject: [messages] [Technical Support & Bugs] Re: Module library
disappeared
Just checked on my work system. It seems to be working fine.
So, it seems to be an individual system problem. It’s also persisted
across completely separate installs of Windows. I have been transferring
my entire Vassal directory (with all the subdirectories that I keep
individual game modules/save files in). So, is there some file I might
be dragging with me that could be causing this?
Read this topic online here:
https://forum.vassalengine.org/t/module-library-disappeared/3563/16
Thus spake pgeerkens:
The only scenarios I can think might be happening are these:
- It was a Java bug fixed in (most likely) build 22 or 23;
- It was a VASSAL bug but that got fixed (inadvertently) in 3.1.14,
probably as part of someone’s general code clean-up. (I just now verified
that, on my system today, 3.1.14 and 3.1.15 behave the same.)- You have been neglecting to carry across the directory:
C:\Users<rindis>\VASSAL
when you moved across systems, and thus have been leaving the Module Manager
database behind, and mistakenly identified the problem with using the
Windows control box to close instead of File|Quit.Pieter
I checked, there were no changes to the MM between 3.1.14 and 3.1.15.
–
J.
Theory 3: I certainly did not bring across anything on the c: drive (I keep all the important stuff on d: just for these occasions). However, in these cases, I do new full installs of Vassal, and then start pointing the module manager to the *.vmod files over at d:\Games\Vassal. I would expect that the install would create whatever user directory information that is needed.
Theory 1&2: I’m pretty sure that my home system is still doing it, I know I’m on top of my Java updates, I’ve been on 3.1.15 since it came out, and before that on 3.1.14 since what feels like forever.
I’ll try to remember to take time tonight to double-check that it is indeed still broken (or at least broken the way I think it is), current Java version, and root around for where my current Vassal install lives.
Good, that verifies my empirical test. What about 3.1.13 to 3.1.14?
Pieter
-----Original Message-----
From: messages-bounces@vassalengine.org
[mailto:messages-bounces@vassalengine.org] On Behalf Of Joel Uckelman
Sent: Monday, January 24, 2011 1:54 PM
To: messages@vassalengine.org
Subject: Re: [messages] [Technical Support & Bugs] Re: Module
librarydisappeared
Thus spake pgeerkens:
The only scenarios I can think might be happening are these:
- It was a Java bug fixed in (most likely) build 22 or 23;
- It was a VASSAL bug but that got fixed (inadvertently) in 3.1.14,
probably as part of someone’s general code clean-up. (I just now verified
that, on my system today, 3.1.14 and 3.1.15 behave the same.)- You have been neglecting to carry across the directory:
C:\Users<rindis>\VASSAL
when you moved across systems, and thus have been leaving the Module
Manager
database behind, and mistakenly identified the problem with using the
Windows control box to close instead of File|Quit.Pieter
I checked, there were no changes to the MM between 3.1.14 and 3.1.15.
–
J.
Ok. I will keep the bug report open until I hear from you tomorrow, one way
or the other.
Pieter
-----Original Message-----
From: messages-bounces@vassalengine.org
[mailto:messages-bounces@vassalengine.org] On Behalf Of Rindis
Sent: Monday, January 24, 2011 1:59 PM
To: messages@vassalengine.org
Subject: [messages] [Technical Support & Bugs] Re: Module library
disappeared
Theory 3: I certainly did not bring across anything on the c: drive (I
keep all the important stuff on d: just for these occasions). However,
in these cases, I do new full installs of Vassal, and then start
pointing the module manager to the *.vmod files over at
d:\Games\Vassal. I would expect that the install would create whatever
user directory information that is needed.
Theory 1&2: I’m pretty sure that my home system is still doing it, I
know I’m on top of my Java updates, I’ve been on 3.1.15 since it came
out, and before that on 3.1.14 since what feels like forever.
I’ll try to remember to take time tonight to double-check that it is
indeed still broken (or at least broken the way I think it is), current
Java version, and root around for where my current Vassal install lives.
Read this topic online here:
https://forum.vassalengine.org/t/module-library-disappeared/3563/19
Thus spake pgeerkens:
Good, that verifies my empirical test. What about 3.1.13 to 3.1.14?
Nothing that I see.
–
J.
Okay, this is crazy. My home system is acting right. It’s been having that trouble for ages…
Okay, cancel the alert. I’ll bring it up more promptly if I ever see it again.
Thank you. I will close the bug as unreproducible.