You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Currently: The pill count, counts everything missed while the window is out of focus. The pill count stays in count with the "missed wins" animation.
Desire: Count everything since the user last opened the transaction history. It is entirely separate from missed wins, and doesn't matter if the window is in focus or not. The pill count should increase as long as the user hasn't opened the tx history.
The text was updated successfully, but these errors were encountered:
Description
---
- added separate `rewardCount` counter for all wins (incl. missed)
Motivation and Context
---
- #1530
How Has This Been Tested?
---
- locally:
https://github.com/user-attachments/assets/2218658f-0032-414b-812c-7a38e4288abc
What process can a PR reviewer use to test or verify this change?
---
- start mining
- ensure counter show for all wins while in focus
- minimize
- ensure counter includes missed wins too
- open rewards
- counter should reset
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
- **New Features**
- Updated the wallet interface to reflect rewards more clearly during
win events.
- Enhanced reward tracking to ensure win outcomes are accurately counted
and displayed.
- Introduced a new method for managing reward counts in the state.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Describe the bug
Currently: The pill count, counts everything missed while the window is out of focus. The pill count stays in count with the "missed wins" animation.
Desire: Count everything since the user last opened the transaction history. It is entirely separate from missed wins, and doesn't matter if the window is in focus or not. The pill count should increase as long as the user hasn't opened the tx history.
The text was updated successfully, but these errors were encountered: