09-02-2022, 03:47 AM
Just at a high level, yes, I think it should be possible to make that work. I currently store position information for every single word/chord on the screen, so I should already have the position information for the sections (although I may need to add some additional code to store the section headers separately so that I can easily reference them). When using the vertical scrolling display mode, I already have a method that I can invoke to scroll the page to a certain pixel position. So I would just need to invoke that method with the position of the next section header along with a little bit of a margin so that the word isn't aligned with the very top of the screen. I would also have to add some code to figure out, based on the current scroll position and page number, what the next section header is, which actually would probably be the most amount of work. The other thing I'd have to handle is how to process things when using other display modes (single page, two page, half page), as I should probably still turn pages even if scrolling isn't possible. With the single page display mode, scrolling may be possible if the user has zoomed in or is using the half page display mode. So I'd just have to make sure to support this feature in all modes in whatever way makes sense.
Mike
Mike