I can fix the visualizer so that when you change GPI parameters, the display changes. The problem I can’t fix is that the image is not saved to the module properly in 3.1. The current ImageOp stuff doesn’t handle the uncaching of images properly. All of the discussion was on the list, I’ll try and pull it together tomorrow.
I now have a more serious problem. I’m trying to create more game piece images but everything I do results in an ‘Untrapped Error - IllegalArgumentException’ error message.
I managed to create a new game piece image with this error message repeating after every keystroke…
I tried the new version of Vassal and now it won’t load the module. It gives an ‘Install Failed - EOF Exception’ error, along with an ‘untrapped error - NullPointerException’ message.
Here’s the error log:
[1998250798]
– OS Mac OS X
– Java version 1.5.0_13
– VASSAL version 3.1.0-beta2
– Manager
[808491624]
– OS Mac OS X
– Java version 1.5.0_13
– VASSAL version 3.1.0-beta2
– Editor
– Feldgrau version 1.0
[1998250798]
java.lang.NullPointerException
at VASSAL.launch.ModuleManagerWindow$MyTreeNode.findNode(ModuleManagerWindow.java:747)
at VASSAL.launch.ModuleManagerWindow$MyTreeNode.contains(ModuleManagerWindow.java:761)
at VASSAL.launch.ModuleManagerWindow.addModule(ModuleManagerWindow.java:589)
at VASSAL.launch.AbstractLaunchAction$LaunchCommandServer.reply(AbstractLaunchAction.java:297)
at VASSAL.launch.CommandServer.run(CommandServer.java:61)
at java.lang.Thread.run(Thread.java:613)
[808491624]
java.io.EOFException
at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2498)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1273)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
at VASSAL.launch.CommandClient.request(CommandClient.java:63)
at VASSAL.launch.Editor.launch(Editor.java:118)
at VASSAL.launch.Launcher.extractResourcesAndLaunch(Launcher.java:135)
at VASSAL.launch.Launcher$1.run(Launcher.java:122)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:461)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:269)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:184)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:176)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
This is the same bugs we where discussing last week
The Game Piece Image Visualizer does not update when you change any parameters
The new image does not get written/cannot be retrieved from the archive. You stated you need to create a new ImageOp subclass that supports the Game Piece Images, plus do something about removing images from the cache.
When I alter the properties of an individual game piece created entirely with the ‘game piece layout’ facility, e.g. the Panther piece (see module Feldgrau), I can’t see the results of my tweak when I drag the piece to the gameboard. I have to close Vassal completely, reopen it, open a new game, and then I can see the results of my tweak.
Now I can’t create another piece without seeing error messages at every step.
I had no trouble opening and/or editing the Feldgrau module using the beta-2 of Vassal.
Is Feldgrau already in the list of modules in the Module Manager? If so, try removing it, then open it again to re-add it.
The Game Piece Image redisplay is definitely broken in that version though.
If you want to make progress soon, I would sugggest you drop back and use v3.0.17 of Vassal. Just ignore the warning message the first time you open the module.