Loop enabled/disabled button should be more obvious
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.4k
- Forks
- 1.3k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 7
Description
The enable/disable loop points button is a bit backwards. It's gray-ed out when it's inactive and just "regular" when it's active.
At a glance, this makes it hard to know when the loop points are enabled:
Gray-ed out from a UI perspective generally means it's not accessible. I think instead, the loop points should behave more like an LED toggle and be very obvious when enabled.
This way when a composer finds their project arbitrarily jumping away from the cursor area, they have a visual indicator as to why.
Contributor guide
No contributing guide indexed for this repository
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 locating the desktop UI entry point for the loop points enable/disable button and reviewing how its inactive and active states are presented. The work is done when the enabled state is immediately distinguishable from the disabled state and the loop behavior remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- design, desktop
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100