[tadawson]

I have been discussing this with Mike, and while I think it is on the list, he suggested I post here to help determine if there is any overall interest to help him prioritize.

Basically, I find that I prefer to run my tablet in landscape in "vertical scrolling" mode with my pedal, since the pedal scroll actions allow me to set how far a pedal press scrolls, as well as how fast (I find that page changes are so fast that it's easy to lose place - this slower partial page scroll allows my eyes to stay on the staff I am playing while the page scrolls throughout the entire piece . . .). The issue is that I also like to use link points to manage repeats/DS/DC/Coda/etc. things, but "Scroll with activate link" actions don't currently exist. Thus, it's either the rapid page turns and risk of getting lost with links, a comfortable scroll without links (risk of getting lost), or use two pedals, one for links and one for scroll (works, but can't look at feet while playing, so very awkward and risky). 

Thus I have asked Mike if he can add "Scroll down or activate next link" and "Scroll up or activate previous link", since all the "moving parts" appear to be there, just not the combination.

Would this be of interest to anyone else? I see a number of comments about half page changes being too quick, and tjis also would work to correct that situation as well.

???

Thanks,

- Tim

[tadawson]

I have to say, that I am very surprised that nobody else has shown interest in this . . . it seems like such a fundamental headache/issue to me.

I guess I don't use the product the way others do . . . 

Hopefully this can still be done at some point.

[Zubersoft]

It's certainly something I can add, I just don't know exactly what the timeline will be. It is something I should be able to slip into a minor update though, as there isn't too much complexity involved.

Mike

[tadawson]

It's certainly something I can add, I just don't know exactly what the timeline will be. It is something I should be able to slip into a minor update though, as there isn't too much complexity involved.

Mike

Thanks Mike . . . I appreciate that. You had just asked that I post the suggestion to gauge interest, and I guess I was both "tickling" it, as well as just expressing my amazememt that I seem to be the only one desirimg this . .  (I'm still curious bout the "Normal" use case for others that circumvents this issue . . . )

[tadawson]

Mike - Any rough estimate of when this may happen? I had sounded like it was quick and simple, but it's been two releases since, so figured I'd ask . . .

Thanks,

- Tim

[Zubersoft]

Fixing bugs was my top priority with those updates. The only minor feature I added was support for a new format string parameter, but that required almost no UI changes, translations, etc. I'll see if I can what you asked for soon.

Mike

[tadawson]

Fixing bugs was my top priority with those updates. The only minor feature I added was support for a new format string parameter, but that required almost no UI changes, translations, etc. I'll see if I can what you asked for soon.

Mike

Understood, and thanks for the update.

- Tim