You missed to tell us:
which one of these do you call the "active" monitor/screen running VSCode
which screen zoom factors did you set in the Windows monitor setup

which one of these do you call the "active" monitor/screen running VSCode

The "active" screen, as I understand it with how FLTK works on windows, is the one the mouse is located on. Moving the mouse to the monitor makes it the active screen. The bug occurs when you launch the application on the active screen with screen scaling enabled (be it vscode, command prompt, file explorer), and then the FLTK window appears on the non-active screen.

which screen zoom factors did you set in the Windows monitor setup

I had it set to 175% when I made this issue, but the bug persists with every screen scale setting except 100%.

Changing the screen scaling on the 4k monitor to 100%, we no longer get the issue:

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.