Microsoft/calculator

keyboard input sometimes broken when multiple instances open

Open

#508 opened on May 16, 2019

View on GitHub
 (7 comments) (0 reactions) (0 assignees)C++ (2,422 forks)batch import
Area: User ExperienceBugPri: 2help wantedtriage approved

Repository metrics

Stars
 (16,196 stars)
PR merge metrics
 (Avg merge 15h 43m) (7 merged PRs in 30d)

Description

Describe the bug If you have more than one instance of Calculator open, which ever instance is not the "original" will lose certain keyboard functions.

For example pressing escape to clear, backspace to backspace and enter to sum. These keyboard keys no longer work on the second instance. I cannot reproduce this 100% of the time. But every time I have encountered this problem, it was when multiple instances were opened. And

Steps To Reproduce

  1. Open calculator
  2. Hold shift and lose focus of the window (easiest way to do this is just to hold shift and left click somewhere outside the window)
  3. Regain focus of the window
  4. Press keys such as enter backspace escape p l x y and probably more

Expected behavior Keyboard input should be observed no matter how many instances of calculator are open.

Device and Application Information

  • OS Build: 10 0 17134 0"
  • Architecture: X64
  • Application Version: 10.1903.21.0
  • Region: en-US
  • Dev Version Installed: False

Note: A team member edited this comment to clarify steps to reproduce.

Contributor guide

Research direction
Investigate how keyboard input is handled across multiple instances. Look at the window message loop and focus event handling. Check if there is a global hook or singleton that interferes.
Tech stack
cpp
Domain
desktop
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C++GitWindows development
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65