1.3 Difficult to seperate marked scale and ghostnotes
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.4k
- Forks
- 1.3k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 7
Description
### Bug Summary
tiny inconvenience as seen in snapshot:
LMMS uses grey scale-marking and grey ghostnotes. That is not a good decision
#### Expected behavior
Ghostnote-color should not be obscured by the color of marked scale
#### Actual behavior
Is obscured..
#### Screenshot
#### Affected LMMS versions
1.3
#### Suggested solution
Ghostnotes could be kept grey, grey is a color connected to our understanding of 'ghosts', but perhaps white is even more logic?
It we go for white-ghosts, then scalemarking can be kept as it is
White ghosts looks like:
Aaaand there is a conflict with notelabels
Perhaps other color schemes is needed
Off-white is not great either
Perhaps going in opposite direction: Black-ghosts...
Preserves notelabels but is not distinctly different from _out-of-scale_ notes
What are _your_ thoughts.
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 reproducing the marked-scale and ghostnote color overlap described in the issue and compare it with the supplied screenshots. Review the affected LMMS interface code and existing color handling, then resolve the competing ghostnote, scale-marking, and notelabel visibility requirements; done means the elements remain visually distinct.
Written by the indexing model from the issue text.
Assessment
- Domain
- design, desktop
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100