Set per-monitor DPI awareness explicitly and verify picks on mixed-DPI desktops

未關閉
#67 1 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 3 天內回覆

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
35/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
冷清
技術堆疊
python

研究方向

Start with the entry point that defines main(), autoclicker/gui/picker.py, and click_engine.py; inspect WindowsAutoclicker.spec and the DPI notes in docs/ARCHITECTURE.md and docs/PERFORMANCE.md. Verify the awareness call runs before Tk and PyAutoGUI load, then use the proposed unit test and manually check picked clicks on both monitors of a mixed-DPI Windows desktop. Done means per-monitor awareness is documented and each click lands on its picked pixel.

由索引模型根據 Issue 內容生成。

描述

bug maintenance priority: low

Why it matters

Picking and clicking only line up if the picker (Tk) and the clicker (PyAutoGUI / Win32) agree on what a pixel is. Today the process's DPI awareness is set implicitly, as a side effect of importing PyAutoGUI, and only to system awareness. On the setups where coordinate bugs actually happen (a 4K laptop at 150% next to a 1080p monitor at 100%), Windows virtualizes coordinates per monitor for system-aware apps. The result may be fine, slightly off, or a blurry overlay on one screen, and nothing in the repo verifies which.

Evidence

  • pyautogui/_pyautogui_win.py calls ctypes.windll.user32.SetProcessDPIAware() at import (system-aware, not per-monitor).
  • No SetProcessDpiAwarenessContext call and no manifest entry in WindowsAutoclicker.spec; nothing in autoclicker/ mentions DPI.
  • autoclicker/gui/picker.py sizes the overlay from GetSystemMetrics(SM_*VIRTUALSCREEN) and reports event.x_root/y_root; click_engine.py moves with pyautogui.moveTo. Correctness on mixed-DPI desktops depends on both sides being virtualized identically.
  • docs/PERFORMANCE.md and docs/ARCHITECTURE.md already list "multi-monitor DPI risk" as a reason to defer a SendInput path.

Suggested approach

  1. Set awareness explicitly and first thing in main() (before Tk and PyAutoGUI load): SetProcessDpiAwarenessContext(DPI_AWARENESS_CONTEXT_PER_MONITOR_AWARE_V2) with fallbacks to SetProcessDpiAwareness(2) and SetProcessDPIAware(). Optionally also embed it in the exe manifest.
  2. Manually verify on a mixed-DPI two-monitor setup: pick a point on each monitor, run, and confirm the click lands on the picked pixel. Record the result in docs/ARCHITECTURE.md.
  3. Add a unit test that main() calls the awareness setter before creating the app.

Done when

  • DPI awareness is explicit, per-monitor v2 where available, and documented.
  • Picks on every monitor of a mixed-DPI desktop click the exact picked pixel (verified once manually and noted in docs).
主要語言
Python
星號
0
分支
2
平均合併
2 天 13 小時
30 天內合併 PR
2

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

TMHSDigital/autoclicker 的其他 Issue

查看 TMHSDigital/autoclicker 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。