[sciurius]

In ChordPro, song parts may be identified as sections, e.g.

Code:

{start_of_verse Verse1}
...lyrics and chords
{end_of_verse}
{start_of_chorus Chorus}
...chorus...
{end_of_chorus}

Would it be possible (i.e. implementable with not too much effort) to use these sections as jump locations?
What I have in mind is a kind of scroll function that, when pressing the pedal, moves the next section to the top of the page.

As usual, an image tells more than 1000 words.

   

Rationale is that I think it is easier to keep track of where you are on the page, especially if someone else is pressing the pedal for you.

Foreseeable complications:

• Only applies to ChordPro files that have sections.
  
• Selectable per song?
  
• Scroll to the next section only if this section is already (partly) visible.
  

What do you think?

[Zubersoft]

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

[sciurius]

Sounds interesting.

In addition (or instead) we could add a special directive to designate a jump location, e.g.

Code:

{mark}
{mark: label}

'Official' defintion: Marks a location in the song. It is up to the viewing and rendering programs to do something sensible with this information.

[ammelch]

This would be a great feature. We had been thinking about a very similar thing the other day.
Instead of turning pages via pedal we'd thought it would be great to highlight the next ChordPo section and just flip the page or scroll down if neccessary.

This would also solve one of our main "issues" when connecting to a master and letting him turn the pages: Different screen sizes and layout settings. Some of us prefer portrait mode, others like landcape mode, some hide the chords to just see the lyrics, etc. which results in very different page numbers for everyone.

If we could jump ahead by sections and not by pages and the app could scroll or flip pages as needed, those issues would all be gone    . 
Currently we are working around this by using lots of {np} tags, basically after every verse or chorus etc. But that way we obviously waste a lot of screen space on the bigger displays to accomodate for the smaller tablets.

I don't even think, the "current" section would have to alway be at the top. Some form of highlighting and if neccessary jumping to the next page might work even better.

[itsme]

How about reusing the adjustable half page separator line (originally added for half page turning) and provide an option like "scroll to next page separator" for vertical scrolling mode. That would work also for PDFs and image files.