Why would a window change from (a) to (b) by use of the “Fit Height” feature? Fit width has an equivalent, non-useful effect:
I can’t see where I’ve gone wrong in the window configuration - the map image is exactly the dimensions of the image and so I would expect that to be dictating the effect of the “Fit” functions. The main map is configured in a similar way and works fine, even if the map is detached from the main toolbar.
What have I missed, or is this a bug?
Which module is this?
Hi,
The behavior you are seeing is because Vassal appears to believe that the Allied and French Hand map boards are exactly 520 pixels bigger in height and width than the background image. Resizing the background image gives a consistent and corresponding change in mapboard size.
I have not seen this before.
A quick glance through the module did not reveal an obvious source (made more difficult as I am not familiar with the game mechanics or how your code implements them). However, I would be looking to see if you have inadvertantly created a map zone or some other reference outside the bounds of the Allied and French Hand map boards.
So no solution but I hope it might point you in the right direction.
Cheers,
Reg.
Thank you @Reg for taking a look. I’ll follow up what you’ve suggested.
You can get the actual map size by using the ‘Save Map as PNG Image’ (Camera) button and check the the resulting image properties or watch when the scroll bars appear and disappear when you resize the map window.
P.S. Also don’t forget to use the editor ‘Tools / Refresh Predefined Setups’ menu item so any module changes are loaded when you do your test runs. (Guilty as charged… I forget all the time!!)
Best of luck.
Reg
I’m suspecting a java bug. Perhaps PlayerHand related.
In the Vassal code, the mapsize() initially gets the correct dimensions - per the image size. The 520 x 520 increase is then added later. The problem is here in PlayerHand.java:
It looks like Vassal is including a off-map (-ve offset) deck in the bounding box. However, negative space is never displayed (correct me if I’m wrong). So, I query why it should be included.
If this is a simple bug, I might be able to fix it (issue #13842 created). I can also look at removing the off-map deck to another place where this won’t happen.
Thanks again @Reg, your hint helped me recognise where the issue was coming from.
