[itsme]

This is a follow up of https://www.zubersoft.com/mobilesheets/f...12765.html and makes a proposal how to solve the issue reported there.

Currently MobileSheets handles a chord grid section (start_of_grid / end_of_grid) as a single object. In case it doesn't fit on the current page it is moved completely to the next page.
This fails badly with long chord grid sections as reported in the thread mentioned above and doesn't agree with the 'line oriented' concept of ChordPro.
Instead a chord grid shall be rendered line by line and as soon as the end of the page is reached it shall be continued on the next page as it is the case with lyrics & chord sections and as it is implemented in the ChordPro reference implementation.

To demonstrate that I created a file with a very long chord grid by duplicating the 'Tiger Rag' chord sequence of the previous thread, TigerRag_x2.pro. 
I had to set the default grid size to a pretty small value to import that file. Then I played around with grid size and portrait / landscape orientation of my tablet.

In portrait orientation grid size 14 was the biggest to show the full song on one page:
   

With grid size 15 page 1 shows only title and subtitle, the chord grid is completely on page 2
       

[itsme]

In landscape orientation page 1 shows only title and subtitle as it is the case in portrait, page 2 cannot be rendered any more and just displays an endlessly spinning circle, MobileSheets has to be killed via task manager.
       
After a restart of MobileSheets the song cannot be opened at all, just shows a black screen, MobileSheets freezes and has to be killed via task manager.

The same ChordPro file rendered with the ChordPro reference implementation 
   

[Zubersoft]

I will certainly try to address all of this with the upcoming changes.

Mike

[itsme]

Thanks a lot

[Zubersoft]

I have this fixed for the next update. Chord grids will now be split across page turns if needed.

Mike

[itsme]

Great. Thank you.