Update index.md

Author: BornToBeRoot

Website/blog/2026-03-04-deep-dive-fixing-dpi-scaling-issues-for-embedded-processes/index.md

@@ -264,16 +264,14 @@ private void UserControl_Loaded(object sender, RoutedEventArgs e)
 
     // VisualTreeHelper.GetDpi returns DpiScaleX/Y as a ratio (1.0 = 96 DPI, 1.5 = 144 DPI).
     var dpi = System.Windows.Media.VisualTreeHelper.GetDpi(this);
-    WindowHost.Height = (int)((ActualHeight - 20) * dpi.DpiScaleY);
-    WindowHost.Width  = (int)((ActualWidth  - 20) * dpi.DpiScaleX);
+    WindowHost.Height = (int)(ActualHeight * dpi.DpiScaleY);
+    WindowHost.Width  = (int)(ActualWidth  * dpi.DpiScaleX);
 
     Connect().ConfigureAwait(false);
     _initialized = true;
 }
 ```
 
-The `-20` offset compensates for a layout quirk introduced by the Dragablz tab control (see [pull request #2678](https://github.com/BornToBeRoot/NETworkManager/pull/2678)).
-
 ## Summary
 
 When you embed a foreign process window via `SetParent`, Windows never forwards DPI change notifications across process boundaries. For console host processes (PowerShell, cmd) use the Windows Console API (`AttachConsole` + `SetCurrentConsoleFontEx`) to rescale fonts directly; for GUI processes (PuTTY) send `WM_DPICHANGED` (0x02E0) explicitly with the new DPI packed into `wParam`. In both cases, apply an initial DPI correction after `SetParent` by comparing `GetDpiForWindow` before and after embedding, and set the `WindowsFormsHost` initial size in physical pixels using `VisualTreeHelper.GetDpi`.