InfiniTimeOrg / InfiniTimeOrg/InfiniTime
Chime kills 2 game.
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.4k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
Verification
- I searched for similar bug reports and found none was relevant.
EDIT: I looked more thoroughly and there seems to be several previous issues relating to this. Notifications disrupting activities.
What happened?
While I was playing 2 the clock turned "whole" and the hourly chime executed - and "executed" my progress in the game.
What should happen instead?
The game should not be interrupted or even dismissed by the chime. The watch should've chimed, but the game screen should've stayed active.
Reproduction steps
- Have chimes on.
- Play game until chime is vibrating.
- Loose all game progress and return to watch face.
Version
1.15.0
This is maybe connected to this issue:
https://github.com/InfiniTimeOrg/InfiniTime/issues/1223_
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing this report with the related issue 1223 and reproduce the failure on InfiniTime 1.15.0 with chimes enabled. Trace how the hourly chime handles the active game screen; done means the chime still occurs without dismissing the game or losing its progress.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100