(06-16-2016, 06:20 AM)sciurius Wrote: Firstly, thanks for the nice page top scroll alignment.
About separating songs, the basic idea is that I just would not expect (parts of) two songs to be shown simultaneously. Checking for a small first / last page would be sufficient.
While at the topic of vertical scroll: I've configured the pedal to scroll 50% of the page. But it does not scroll 50% of the page, it scrolls 50% of the screen. The difference is the black area that is between pages. So the first page (we're talking about ChordPro, so MSPro makes up the page) covers the whole screen (1280 px). Tap pedal and it scrolls 640px up, showing the lowest 640px of the first page, some 20px(?) black bar, and 620px of the next page. One more pedal tap scrolls up 640px, the black bar is now on top and at first glance it looks as if the second page is displayed. But two taps later there's 20px of the 2nd page on top, then the black bar, and then 600px of the 3rd page. You get the idea: while progressing through the pages the black bar shifts further down. I seem to recall that some earlier version did this (more) correctly.
I'm not sure that separating songs in the vertical scrolling mode really makes sense in a setlist. That's kind of the point of the setlist - to create a continuous playback through all of the songs. If the songs should be separated, I would actually argue that you should disable the "Always Load Whole Setlist" and enable the "Automatically Load Next Song". Then you can page through the songs independently, switch between them as needed, and never have to worry about overlap between songs. I wonder if I should be trying to make this mode of operation something that is easier to trigger or switch between...
As far as scrolling, all scroll amounts are measured as a percent of the current page being scrolled. I do appear to be accounting for the gap between pages in some places, but not others, so I think it's just a bug I need to fix.
UPDATE:
Found the bug in the pedal scrolling where I'm not accounting for the gap and I also found a similar problem that can happen in the automatic scrolling.