-
Notifications
You must be signed in to change notification settings - Fork 865
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot see the left<-->right scrollbar at bottom of PTM (unless up<-->down is at lowest) #1144
Comments
Do you have a suggested solution? Perhaps always have that part visible and only scroll the top portion? |
We always want it visible. I think we want to scroll the same way as it does now, but it needs to always be visible. I remember that there were technical challenges to this. Is this implementation possible? |
I think we can do it, but I want to focus on the sorting bug first (#1147). |
@pikurasa is this issue still relevant? I could not find the PTM block |
PTM === phrasemaker |
The issue is different from when this was first reported, but the fundamental problem is the same. If the user creates something with a lot of columns and rows, it is hard to see the entire graph. I don't know if scrolling is necessarily the design-feature to fix this. Test file (FYI, There is some issue with repeats in the phrasemaker, which is why I do not simply do longer repeats for the scalar step. I will report in a separate issue.) |
Is this still an issue? You should be able to drag the window around w/o going to the scroll bar. |
This video shows how someone would need to scroll if they had a lot of notes in the PhraseMaker: |
This is still an issue, and is particularly pronounced when the user puts their widget frame into "fullscreen." I am open to different methods of solving this issue (not just "scrolling" per se), but the user should be able to somehow see all the pitches, including during widget preview playback. |
If the matrix is large, you cannot see the bottom scroll unless you are all the way at the bottom.
The text was updated successfully, but these errors were encountered: