I checked current master and this appears to have been addressed already.
The non-live wxSplitterWindow sash tracker no longer uses wxScreenDC screen coordinates. It now draws a window-relative overlay rectangle via wxOverlay, with the relevant change introduced by commit a381758 (Use wxOverlay to show sash feedback in non-live resize mode in wxSplitterWindow).
The current implementation in wxSplitterWindow::DrawSashTracker() builds the tracker rectangle in client coordinates and passes it to the overlay drawing helper, so the original DPI virtualization mismatch between ClientToScreen() coordinates and wxScreenDC drawing should no longer apply.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you authored the thread.![]()