Apologies if I should post this reply elsewhere, but I have a strange issue with Vassal since beta 3 which still don’t seem cured by 4397.
This is an issue which appears as soon as I start Vassal, click on edit module, open properties for a piece in an at start deck. This piece has a basic piece trait with no image, followed by a layer trait with 3 levels. The first level has no image. The levels follow the value of a global property, called DUMMY, say, defined at map level.
The history of this issue is as follows:
Beta 1 and 2: no problem
Beta 3: just opening the module gives a NULL POINTER EXCEPTION and Vassal just hangs (the reason could be some other piece, though, for what I know…)
Beta 4: the basic piece is not happy with the null image (IMAGE NOT FOUND), ditto for the layer trait (IMAGE NOT FOUND for the first level in the layer)
Beta 4397: same as above except on first opening the piece properties window it immediately gives a BAD DATA. NOT A NUMBER: NULL error
What’s more, when clicking at the top of the properties window for this piece in the editor (where the piece image should show) the chat/report window reports error finding the global property DUMMY. However, the DUMMY variable is regularly present in the global properties of the map where the piece in question is, though. I guess that maybe the editor mistakenly looks for global properties at module level, for the limited purposes of that piece preview window.
I think I read, time ago, that the various issues with null images had been solved… or had they not? Any clue?
On a side note, beta 4397 now messes up positioning of some of my text labels (no problems with beta 4). But I remember that I had to purposefully misplace them at the time, to make them show where I wanted them… so maybe it’s just a matter of putting them back where they should really go now…