On Tue, 16 Dec 2025 19:02:41 GMT, Martin Fox <[email protected]> wrote:
>> Definitely. We don't need to worry about Windows 8 or earlier, but it's >> premature to break Windows 10. > > I don't want to stop supporting Windows 10. I'm referring specifically to > Windows 10 RTM, the very first version of 10, which has fallen entirely out > of Microsoft's support system. If we only need to support versions of Windows > that Microsoft is supporting that would be Windows 10 2016 (1607) in which > case there's no need to mess with all the DLL and function pointer retrieval > in this code. You can just issue direct calls to SetThreadDpiAwarenessContext > and friends. > > I will add that though we might say in this thread that we don't need to > worry about Windows 8 or earlier I really and truly could not find any public > statement to that effect anywhere. If we removed that path, then for Windows 10 < 1607, we wouldn't be able to skip coordinate mapping for the usual (99.9%) case when the Java process is running with per-monitor DPI awareness. This wouldn't cause JavaFX to stop working, we'd just be back at the status quo where we don't account for the visible window frame. We still need to dynamically load the function though, as it definitely won't be available on Win10 < 1607. ------------- PR Review Comment: https://git.openjdk.org/jfx/pull/1982#discussion_r2624450742
