rust-windowing / rust-windowing/winit

ghost keyboard input when focus of window changed in Windows.

Open
#2,175 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

C - needs investigation DS - win32
Dominant language
Rust
Stars
6.2k
Forks
1.3k
Avg merge
2d 19h
Merged PRs (30d)
9

Description

Environments:
Windows 10 Enterprise build 19041.1415
Korean language
winit = "0.26.0"

problem:
when I change focus of window, KeyboardInput event is polled.
When losing focus, VirtualKeycode::Kana with scancode 56 has polled.
When gaining focus, two event has polled in a row. scancode 0 was first, VirtualKeycode::Kana with scancode was second.
state of all of them was released.

step to reproduce:

Event::WindowEvent { window_id, event } if window_id == self.window.id() => {
    match event {
        WindowEvent::KeyboardInput { input, .. } => {
        println!("keyboard: {:?}", input);
    }
    _=> {}
}

제목 없음

Contributor guide

Open the contributing guide

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.

Research direction

Start by reproducing the WindowEvent::KeyboardInput behavior on Windows 10 with Korean input and winit 0.26.0, focusing on events emitted when window focus changes. Done means focus changes no longer produce the reported spurious released events, including scancode 0 and VirtualKeycode::Kana.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
desktop, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.