<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Windows on Dev's Log</title><link>https://piot5.github.io/devs_log/tags/windows/</link><description>Recent content in Windows on Dev's Log</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Sat, 03 Jan 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://piot5.github.io/devs_log/tags/windows/index.xml" rel="self" type="application/rss+xml"/><item><title>Chapter One: Display Handshake Churn</title><link>https://piot5.github.io/devs_log/posts/chapter-one-display-handshake-churn/</link><pubDate>Sat, 03 Jan 2026 00:00:00 +0000</pubDate><guid>https://piot5.github.io/devs_log/posts/chapter-one-display-handshake-churn/</guid><description>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 &amp;ldquo;Display Handshake Churn&amp;rdquo; 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:</description></item></channel></rss>