On Windows, the MS-DIAL 5.5 main window can appear partially outside the visible monitor area even when the window is maximized. In the attached screenshot (Screenshot 2026-04-29 084742.png), the capture starts at the physical top-left corner of the monitor, but the MS-DIAL window content is already clipped on the left and top edges. This makes parts of the ribbon/title area inaccessible.
The issue appears to be related to maximized window bounds rather than ordinary WPF content layout. MS-DIAL 5 uses a WPF RibbonWindow as the main window. Unlike older MS-DIAL4 projects, the MS-DIAL5 GUI project currently does not include an application manifest declaring Windows/DPI awareness. The main window also does not handle WM_GETMINMAXINFO, so Windows/WPF default maximize calculations can allow the native resize frame to extend beyond the monitor work area.
A patch created by a chatbot is attached. It needs to be tested by specialists. Or just use the idea of fixing the manifest file as used to be in version 4.
[MSDIAL-5.5-window-bounds.patch](https://github.com/user-attachments/files/27194941/MSDIAL-5.5-window-bounds.patch)
On Windows, the MS-DIAL 5.5 main window can appear partially outside the visible monitor area even when the window is maximized. In the attached screenshot (
Screenshot 2026-04-29 084742.png), the capture starts at the physical top-left corner of the monitor, but the MS-DIAL window content is already clipped on the left and top edges. This makes parts of the ribbon/title area inaccessible.The issue appears to be related to maximized window bounds rather than ordinary WPF content layout. MS-DIAL 5 uses a WPF
RibbonWindowas the main window. Unlike older MS-DIAL4 projects, the MS-DIAL5 GUI project currently does not include an application manifest declaring Windows/DPI awareness. The main window also does not handleWM_GETMINMAXINFO, so Windows/WPF default maximize calculations can allow the native resize frame to extend beyond the monitor work area.A patch created by a chatbot is attached. It needs to be tested by specialists. Or just use the idea of fixing the manifest file as used to be in version 4.