Add Taskbar Custom Hover Zone mod implementation

[ksryou3224926-jpg]

Adds a new Windhawk mod that restricts the taskbar auto-hide hover trigger area to a customizable center zone.

Summary

When using Windows taskbar auto-hide, moving the mouse cursor anywhere near the bottom edge triggers the taskbar. This mod limits the active mouse trigger area to a customizable central section (e.g. 30% to 70%) to prevent accidental pop-ups while using scrollbars or full-screen apps.

Key Features

• Configurable activation range (zoneStartPercent and zoneEndPercent).
• Supports both Windows 10 (Win32 SetTimer) and Windows 11 (ViewCoordinator) architectures.
• Multi-monitor support.

Changelog

If this pull request updates an existing mod, describe the changes below:

• Initial release of Taskbar Custom Hover Zone

Mod authorship

If this pull request introduces a new mod, please complete the section below.

This mod was created by:

• The submitter, without AI assistance
• The submitter, with AI assistance
• Claude
• ChatGPT
• Gemini
• Another AI (please specify):
• Other (please specify):

Please select the options that best apply. Your selection does not affect the acceptance criteria, but it helps reviewers understand the context of the code and provide relevant feedback.

[m417z]

Submission review

Note: This review was done by Claude, and then refined manually. Due to the amount of submissions, doing a fully manual review for each pull request is no longer feasible. Thank you for understanding.

Please address the following issues. The items in the collapsed sections are optional, so it's your call whether to address them.

---

This overlaps almost entirely with an existing mod — taskbar-auto-hide-custom-activation-area. That mod already does exactly what this one does — restrict the auto-hide mouse trigger to a configurable region of the taskbar — and the two are clearly related: this PR uses the same magic timer id (kTrayUITimerUnhide = 3), the same Win11 reason codes (7/8), the same UpdateIsExpanded symbol string, and the same Taskbar.View.dll → ExplorerExtensions.dll fallback. Functionally, this submission is a strict subset (a single center %-% band vs. an arbitrary comma-separated list of pixel/percent regions), and it drops several correctness details the existing mod gets right. Windhawk's strong preference is to extend an existing mod rather than merge a near-duplicate — duplicates fragment the catalog and confuse users. If there's a genuine gap in the existing mod (e.g. the "edge margin" idea), please open an issue/PR against it instead of shipping a parallel mod. As it stands there's no good reason it should be merged as a separate mod.