https://piot5.github.io/devs_log/Recent content on Dev's LogHugo -- gohugo.ioen-usMon, 13 Apr 2026 00:00:00 +0000https://piot5.github.io/devs_log/posts/chapter-three-ghost-monitors/Mon, 13 Apr 2026 00:00:00 +0000https://piot5.github.io/devs_log/posts/chapter-three-ghost-monitors/REGISTRY LAYER (Persistent) SYSTEM\...\DISPLAY ↳ EDID (Cached Serial) ↳ InstanceID (GSM5B09...) Result: Identity Found GDI LAYER (Hardware) EnumDisplayMonitors() ❌ Detached: No HMONITOR ❌ DDC/CI: Fail (No Pulse) DISPLAYFLOW BRIDGE 1. scan.rs → Fetch Serial from Registry 2. synth.rs → Map InstanceID to Profile 3. Wake Up → ChangeDisplaySettingsExW Action: Create Live Handle After Wake: DDC/CI commands enabled THE EDID VOID: Identity vs. Accessibility In a perfect world, every monitor would always be reachable.https://piot5.github.io/devs_log/posts/chapter-two-talking-to-the-silicon/Thu, 05 Mar 2026 00:00:00 +0000https://piot5.github.io/devs_log/posts/chapter-two-talking-to-the-silicon/Software-side display management (resolution and position) is only half the battle. To truly control a workspace, we need to talk to the monitor’s internal firmware. This is where DDC/CI (Display Data Channel Command Interface) comes into play. 1. The Physical Monitor Bridge In Windows, a “Logical Monitor” (GDI) is not the same as a “Physical Monitor” (The actual plastic and glass hardware). As seen in ddc.rs, we must first bridge this gap using the GetPhysicalMonitorsFromHMONITOR API.https://piot5.github.io/devs_log/posts/chapter-one-display-handshake-churn/Sat, 03 Jan 2026 00:00:00 +0000https://piot5.github.io/devs_log/posts/chapter-one-display-handshake-churn/Managing monitor setups—resolutions, positions, and orientations—is a notorious pain point. While Windows provides a UI, automating it involves navigating the deep waters of the GDI (Graphics Device Interface). 1. Neutralizing “Display Handshake Churn” If you change your resolution manually, the screen flickers or goes black. Doing this for four monitors sequentially would cause the system to hang and windows to jump randomly across the desktop. The solution is a two-phase commit approach: