I have a module that I have created. I had a large number of counters to add to it, so I manually added them to the buildFile - which normally works fine. As I went, after adding each batch I checked that the module was OK.
I have just discovered that I can still open the module, and it seems to play fine (as far as it goes - it isn’t complete yet) but that I can no longer edit it. If I try to edit it, nothing happens at all - nothing appears in the error log, no hourglass, nothing. Any ideas where I should look for diagnostics, before going back a day and gradually working through all the changes to the buildFile, line by line, to figure out which change broke editting (without affecting playing)?
To repro, I just select “Edit Module” for that module, and nothing happens. No error message, no module appearing.
Running on linux, kubuntu 10.04 64 bit. An elderly 3GHz AMD box with a single processor and a cheap old Radeon video card, though I can’t believe that is relevant here.
Java version :
java version “1.6.0_21”
Java™ SE Runtime Environment (build 1.6.0_21-b06)
Java HotSpot™ 64-Bit Server VM (build 17.0-b16, mixed mode)
I have a module that I have created. I had a large number of counters to
add to it, so I manually added them to the buildFile - which normally
works fine. As I went, after adding each batch I checked that the module
was OK.
I have just discovered that I can still open the module, and it seems to
play fine (as far as it goes - it isn’t complete yet) but that I can no
longer edit it. If I try to edit it, nothing happens at all - nothing
appears in the error log, no hourglass, nothing. Any ideas where I
should look for diagnostics, before going back a day and gradually
working through all the changes to the buildFile, line by line, to
figure out which change broke editting (without affecting playing)?
To repro, I just select “Edit Module” for that module, and nothing
happens. No error message, no module appearing.
Running on linux, kubuntu 10.04 64 bit. An elderly 3GHz AMD box with a
single processor and a cheap old Radeon video card, though I can’t
believe that is relevant here.
Java version :
java version “1.6.0_21”
Java™ SE Runtime Environment (build 1.6.0_21-b06)
Java HotSpot™ 64-Bit Server VM (build 17.0-b16, mixed mode)
I have a module that I have created. I had a large number of counters to
add to it, so I manually added them to the buildFile - which normally
works fine. As I went, after adding each batch I checked that the module
was OK.
I have just discovered that I can still open the module, and it seems to
play fine (as far as it goes - it isn't complete yet) but that I can no
longer edit it. If I try to edit it, nothing happens at all - nothing
appears in the error log, no hourglass, nothing. Any ideas where I
should look for diagnostics, before going back a day and gradually
working through all the changes to the buildFile, line by line, to
figure out which change broke editting (without affecting playing)?
To repro, I just select "Edit Module" for that module, and nothing
happens. No error message, no module appearing.
Running on linux, kubuntu 10.04 64 bit. An elderly 3GHz AMD box with a
single processor and a cheap old Radeon video card, though I can't
believe that is relevant here.
Java version :
java version "1.6.0_21"
Java(TM) SE Runtime Environment (build 1.6.0_21-b06)
Java HotSpot(TM) 64-Bit Server VM (build 17.0-b16, mixed mode)
Thanks for the replies. Rebooting fixed this, so I feel a bit of a fool, but I’m still puzzled.
Just for clarity, my PC was in a state where it could :
open any one of a dozen modules to play
edit any module, except that one particular version of the module I’m working on
Trying to edit that version of that module just led to nothing happening
I had tried all the obvious things
shutting down and restarting the java process
changing the module (by editting the buildFile), to try to figure out what it was complaining about
removing the module from the list of modules that VASSAL was remembering, then selecting it by specifying the path
None of these worked, and no errors were reported either to screen (I was running VASSAL from a console, at least some of the time) or to the Error log you can view through the VASSAL window.
This morning I tried on another computer, which worked fine, so I went back to the first computer and tried again - and it was all working fine after rebooting overnight.
I’m left thinking something like “cached shared library”, but that makes no sense. I might as well say “malevolent code pixies”.
So thanks again for your time, and apologies for not thinking to reboot before posting!