two very minor items…
- on the Linux releases, when you make a sh script you do not have a full path specification for the location of the module launcher. so it works fine when clicked directly in its spot but if you make a shortcut to it from another directory the launch fails because it is not the current directory.
I find I have to change…
dirname "$0" && java -classpath lib/Vengine.jar VASSAL.launch.ModuleManager “$@”
dirname "$0" && java -classpath /home/john-murphy/VASSAL-3.1.0-beta5/lib/Vengine.jar VASSAL.launch.ModuleManager “$@”
now… maybe this is something in my setup related to classpath but I am using the default setup out of the package manager’s java box.
also, a fix could be difficult because you do not know the location where it will be installed, and even worse where the shortcut could be run from.
(and it is not a difficult problem for the, what, five or ten?, vassal linux users to figure out and edit the script post-extraction)
- module editor… which I know is a low priority… some (most really) windows can grow quite large if you hog-wild with command keys for options, and there is no mechanism built into the windows to permit them to become scrollable. so at some point they push the keys to close them or edit them off the screen.
I am not sure maybe I had already reported this but I do not think so. it is in a grey area between bug and rfe.