Pan limit for score main view
Currently, the score in the "MainView" is drawn on an infinite canvas and one can get lost by dragging.
If pos1 or end buttons are unknown to the user, there is no way to get back!
| Attachment | Size |
|---|---|
| Bildschirmfoto1.jpg | 37.34 KB |
Comments
I think this is important, but you can get back by using the "home" and "end" keys.
In reply to I think this is important, by xavierjazz
As I said, there are keys to get back, but they shouldn't be needed because scrolling too far away isn't useful at all.
In reply to As I said, there are keys to by TromboRafi
Yeah, but I always like to add the info for someone who is looking for help.
Regards,
In reply to Yeah, but I always like to by xavierjazz
Am I right to assume that the relevant code for this lies in Scoreview.cpp?
I want to avoid wrapping my head around a file which wont help.
Thanks!
In reply to Scoreview.cpp by TromboRafi
I brought up this issue a few years ago, someone tackled it months ago and submitted a PR, but it was overruled. Personally I don't see any reason to have an infinite canvas, as it's the music where the focus should be. It just causes issues.
However, be prepared to have this change rejected.
In reply to I brought up this issue a few by schepers
Wondering why... I'm sure there was a good reason though. Maybe it was not a good implementation. I currently learn to code in my free time, I hope by the time I can do this myself I wont have to.
This issue was blogged about at https://simplyrobert.wordpress.com/2015/02/17/musescore-2-0-beta/
"The application workspace has no idea what the dimensions of your document are, so you can scroll it to oblivion. Of the interface I’d like to see fixed, this one is at the top of my list."
@schepers if you could find the PR related to this, perhaps the proposed fix could be revisited.
In reply to This issue was blogged about by Thomas
See http://musescore.org/en/node/8808, there is a patch attached there. However I think MS switched to using GIT around this time, and I don't see the updated patch mentioned by Lasconic. His patch was around Apr/2012, and the first patches in GIT start around May/2012.
In reply to See by schepers
I hadn't seen this thread yet. Very useful to read through the discussion. Thx schepers.