12-27-2023, 02:44 AM
Hello,
I'll respond to each comment below:
When using vertical scrolling mode and zooming in, I can only pan up/down but not sideways.
It's designed this way to prevent accidental panning, as the idea is that users wouldn't be zooming and panning while playing a score in a performance (the page should already be set up as the user wants it to be, and it's generally better to use cropping than zooming to remove margins). You can pan with a two finger gesture though if desired. I should mention that with the single page display mode, you can go into the Zoom/Pan settings, enable "Reset pan and zoom on load", and then if you zoom in on a page, you can pan it with a single finger. You won't be able to turn the page until you zoom back out though. A two finger tap resets the zoom by default.
When page turn by tapping on sides is disabled, it’s not possible to show/hide the overlay by tapping on sides.
This is an oversight. I'll fix that for the next update - thanks.
Zooming in/out in vertical scroll mode sometimes centers the page I'm trying to use zoom on. For example, if I have half of one page and half of another page on the screen, and then try to zoom in one of them, that page sometimes gets centered and fills the entire screen.
I'll have to dig into this one. Some of the layout logic for ensuring pages don't end up in an invalid state is probably getting triggered in an undesired way, resetting the page to be aligned with the top of the screen.
I think it would be nice to be able to zoom out using double tap, I think it’s the default behavior on Apple devices, and it’s hard to break this habit.
While I can certainly consider supporting that, it does mean that single taps will be processed slower, because I always have to wait to ensure the user isn't double tapping before processing a single tap. So my preference is to keep the app more responsive and use a two finger tap to reset the zoom, but if enough users want the double tap, I can certainly support it. I could also make it configurable in the touch settings to keep everyone happy.
One thing I miss from forScore is the tie/slur and square pedal marking
One of the updates is going to be dedicated to adding more functionality in the annotation editor including slurs, pedal markings, more staff options, etc.
When opening the overlay, the PDF jumps around quickly, perhaps it would feel nicer if it had some animation and moved together with the overlay.
This one is problematic, as the app just performs a layout pass after the overlay is displayed, causing pages to immediately shrink down. Having that be animated requires slow changes over time, so it would require changing a fair amount of code. Having said that, I agree that it would look a lot nicer to have it be animated.
You'd have to embed the annotations in the first song (which can be done through the annotations editor), and have both songs share the same file. That's the only way to ensure the same annotations are always displayed in both.
Mike
I'll respond to each comment below:
When using vertical scrolling mode and zooming in, I can only pan up/down but not sideways.
It's designed this way to prevent accidental panning, as the idea is that users wouldn't be zooming and panning while playing a score in a performance (the page should already be set up as the user wants it to be, and it's generally better to use cropping than zooming to remove margins). You can pan with a two finger gesture though if desired. I should mention that with the single page display mode, you can go into the Zoom/Pan settings, enable "Reset pan and zoom on load", and then if you zoom in on a page, you can pan it with a single finger. You won't be able to turn the page until you zoom back out though. A two finger tap resets the zoom by default.
When page turn by tapping on sides is disabled, it’s not possible to show/hide the overlay by tapping on sides.
This is an oversight. I'll fix that for the next update - thanks.
Zooming in/out in vertical scroll mode sometimes centers the page I'm trying to use zoom on. For example, if I have half of one page and half of another page on the screen, and then try to zoom in one of them, that page sometimes gets centered and fills the entire screen.
I'll have to dig into this one. Some of the layout logic for ensuring pages don't end up in an invalid state is probably getting triggered in an undesired way, resetting the page to be aligned with the top of the screen.
I think it would be nice to be able to zoom out using double tap, I think it’s the default behavior on Apple devices, and it’s hard to break this habit.
While I can certainly consider supporting that, it does mean that single taps will be processed slower, because I always have to wait to ensure the user isn't double tapping before processing a single tap. So my preference is to keep the app more responsive and use a two finger tap to reset the zoom, but if enough users want the double tap, I can certainly support it. I could also make it configurable in the touch settings to keep everyone happy.
One thing I miss from forScore is the tie/slur and square pedal marking
One of the updates is going to be dedicated to adding more functionality in the annotation editor including slurs, pedal markings, more staff options, etc.
When opening the overlay, the PDF jumps around quickly, perhaps it would feel nicer if it had some animation and moved together with the overlay.
This one is problematic, as the app just performs a layout pass after the overlay is displayed, causing pages to immediately shrink down. Having that be animated requires slow changes over time, so it would require changing a fair amount of code. Having said that, I agree that it would look a lot nicer to have it be animated.
When I create a snippet of some pages from a bigger PDF, it creates a “reference” to those pages instead of creating a new copy, but annotations are stored differently for the original file and the snippet. Is it possible to also share annotations (i.e. when I annotate the snippet it also annotates the original PDF)?
You'd have to embed the annotations in the first song (which can be done through the annotations editor), and have both songs share the same file. That's the only way to ensure the same annotations are always displayed in both.
Mike