Knob will erroneously say a value has changed at lower and upper limits
- Dominant language
- Rust
- Stars
- 2
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
The knob will continue to say it is changed when hitting the lower and upper boundaries of its range, provided that the mouse is moving in the same direction. Once the knob hits a range boundary, it shouldn't say that it has changed until it moves the other direction.
This is what the console looks like if I continue to move the mouse upwards after hitting the upper boundary of 1.
```
knob changed: 0.66
knob changed: 0.66
knob changed: 0.68
knob changed: 0.70
knob changed: 0.72
knob changed: 0.81
knob changed: 0.86
knob changed: 0.96
knob changed: 1.00
knob changed: 1.00
knob changed: 1.00
knob changed: 1.00
knob changed: 1.00
knob changed: 1.00
knob changed: 1.00
knob changed: 1.00
knob changed: 1.00
```
Additionally, the GUI may rotate when the knob changed value stays the same, leading to duplicate values.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.