The attached ChordPro file causes an endless loop in MobileSheets so that I have to kill it via TaskManager.
While trying "Import Local File" MS hangs showing the "Import Settings" dialog, during a batch import the progress dialog shows "Importing File #185 - TigerRag.pro" and that's it.
Same behaviour on Win10 and Win11.
At first glance I cannot see anything wrong with the file, the ChordPro reference implementation renders it without problems.
I tried to identify what causes the problem. Assuming there are some faulty characters I removed line by line from the file in the last post. Probably the syntax is OK and there are no faulty characters.
It showed that there's an issue because you try to keep the whole grid section on the same page. As soon as I remove enough lines, the import works within seconds as with other ChordPro files I used before. But there's a certain number of lines where the song is displayed correctly in portrait orientation but shows just a black screen in landscape orientation. This is affected by the screen size and the size of the grid font (Grid Size) that is specified in Default Text Display Settings. Reducing Grid Size fixes both the issue with the black screen and the endless loop issue of my previous post. Nevertheless MobileSheets should not freeze, never.
In my case e.g. Grid Size 18 works and creates the attached result, Grid Size 40 caused the reported issues.
Duplicating all the grid lines to make sure the song is bigger than one page and rendering it with the ChordPro program V 6.070.5 shows, that the reference implementation just inserts page breaks wherever it is appropriate, the same as in lyrics and chords, see TigerRag_twice.pdf
01-26-2025, 01:32 AM (This post was last modified: 01-26-2025, 01:33 AM by Zubersoft.)
It's not easy for my code to split a chord grid over multiple pages with how the chord grid parsing/processing is currently implemented (each line is not independent of the others). I'd rather not implement it that way, as it would require significant changes to the code. Instead, what I think I'm going to do is dynamically split apart grid sections if needed so that will insert a new {start_of_grid}/{end_of_grid} section with the remainder of the chord grid lines that couldn't fit on the current page. I'll have to do some testing, but I believe the end result will be the same if I do this.
