Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Should Mouse use WM_MOUSELEAVE for Win32 raw input

Open
  • Is something wrong?
#424 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp
Domain
desktop

Research direction

Inspect the Win32 Mouse implementation for relative raw input and its current WM_MOUSEHOVER handling. Compare whether WM_MOUSELEAVE should also be handled for multi-monitor behavior, and validate that the resulting pointer-state behavior is more robust.

Written by the indexing model from the issue text.

Description

input

Currently the Mouse implementation for Win32 with raw input for relative movement only uses WM_MOUSEHOVER. Would it be more robust if it also used WM_MOUSELEAVE, perhaps on multi-monitor systems?

Dominant language
C++
Stars
2.9k
Forks
537
Avg merge
2d 21h
Merged PRs (30d)
6

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/DirectXTK

All issues in microsoft/DirectXTK

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.