I found another HDPI Scaling issue. Maybe you are already aware of it:
In Vietnam 1965/1975 version 4.3.4 (vassalengine.org/mediawiki/i … 4.3.4.vmod)
You have a button that overlays s string of 1hex area of effects to mark a boundary. (You make them appear with the 2 buttons (red/blue squares) to the right of the 1D6 and 2D6 buttons.
At 100% these overlay appears in the correct manner. At 125% it appears somewhere else (at the 100% position I think).
I have an unpublished The Longest Day module that uses a similar technique. There too the issue appears.
The Vietnam module has 2 different uses of the Area of Effect trait. One is to highlight the hexes around some counters. That one works correctly at any scaling.
The differences I see is that while both are “Fixed Radius”, the one that fails has a radius of 0 (area only applies on origin hex).
econ
The other difference is that the one is set as “Always visible” (it is hidden when button pressed by a change in the Map Shading settings probably) whereas the one that works has “Always visible” unchecked.
Hope that helps.
I ran the latest 3.3.0-svn9343 on my iMac 5K (Retina), screen set to Scaled resolution. The module shows correctly
Then I dragged this window over to my external FullHD (non-Retina) monitor. This image is at the same zoom level as the first image:
As you can see the board is clipped at the bottom, the first time I zoomed out from 100% to 44% to view the entire board the clipped part was black until I resized the panel to repaint it.
Not only is the image drawn at the wrong size, the position calculations are also all off. I can not click on anything as it’s not where it’s being drawn.
3.3.0-svn9343 on my iMac 5K (Retina), screen set to Scaled resolution.
Selection rectangle drawn is completely wrong. In this image I am dragging from the small cross (left top) to about where the big cross is (right bottom). The selection when I let go is correct, despite the rectangle visual.
The only silver lining I can provide is that macOS doesn’t allow window spanning across multiple displays at once. It’s either on the one (and clipped on the side), or on the other (and clipped on the opposite side). So a single window can’t be at multiple scale factors at once.
Playing a game of Memoir '44 against myself, and when my ‘opponent’ moves on the other VASSAL client it draws a red outline of his moved unit in the wrong place on my VASSAL client. This only appears when the remote opponent has moved.
The (too small) red outline drawn on the river on the top left near the Pegasus Bridge is from my opponent moving a unit near the Orne river on the right:
The Windows client on the non-HiDPI display draws correctly when I move something on the Mac.
I messed with this module a bit in 3.2.17 and the most recent test build and wasn’t able to see what those buttons do. What are the steps for triggering this?
I might have found a solution to the problem of dragging between screens with different pixel scaling. (It occurred to me that there may also be a similar problem on systems where you can change the pixel scaling on the fly, which I guess is possible on Windows, and what I’m working on would solve that problem as well.)
What’s with the giant grey burritos east of Pegasus Bridge?
This ought to be good…Screen shot please!
On Friday, April 10, 2020, 10:35:04 AM CDT, uckelman uckelman@nomic.net wrote:
I might have found a solution to the problem of dragging between screens
with different pixel scaling. (It occurred to me that there may also be
a similar problem on systems where you can change the pixel scaling on
the fly, which I guess is possible on Windows, and what I’m working on
would solve that problem as well.)
What’s with the giant grey burritos east of Pegasus Bridge?
The giant grey burritos are rolls of barbed wire. The boardgame comes with pieces like this in green and blue to represent wire positions for each side. In the Memoir '44 Online game they are these grey ones.
This might solve the problem of dragging windows between screens with different scale factors, and also might give a correct result if you can change the scale factor on a screen while VASSAL is running.
3.3.0-svn9345 solves the scale factor problem, I can drag the window
back and forth and it adjusts correctly. Selection on the map is also
correct.
Great. Thanks for testing.
The difference between this and the previous build is that the system
scale factor is fetched for each reapaint, so if it changes the next
repaint will pick that up.
On the non-Retina display the drag rectangle is correct. On the Retina
(scaled) display the drag rectangle is still drawn wrong.
/pic5334981.png)
/pic5334982.png)
/pic5335083.png)
/pic5335888.png)
