[ARS]

Since the last major release (I think 3.9.29), I have noticed a change in the display of my ChordPro files (*.cho).

It occurs when when a chord is encoded to display after the last word of a line.  For example, my .cho file is encoded as:  

     [E*]Don't you feel it growin', day by day?[  ][A*]


BEFORE the release it was displaying as (which is the way I wanted):

     E*                                      A*
     Don't you feel it growin', day by day?


AFTER the release it is displaying as: 

     E*                                       A*
     Don't you feel it growin', day by day  ?


The workaround I have been using for new songs is to replace '[bb]' w/ 'b[ b]'.  However, hundreds of existing songs in my library are impacted by the change, and it would require a lot of work to go back and fix them all.

Please have a look at this.

Kind regards, ars

PS  I have include a sample .cho file & a screenshot

   
  the DOOBIE BROTHERS - Listen To The Music - LYRICS.txt (Size: 2.01 KB / Downloads: 5)

[Zubersoft]

If multiple chords are grouped side by side, MobileSheets is trying to keep them both over the same letter, so it spaces things out to make things line up properly. However, I'm not sure why it's doing that improperly at the end of the line, so I'll have to look into it. It's most likely related to the fixes that were put in place for empty chords [ ] as another user reported a problem with the measurements related to that at the start of a line, and those fixes are causing this issue. There are many ways to prevent this problem though, including:

1) Putting a space after the last letter, such as day by day? [ ][A*] instead of day by day?[ ][A*]
2) Putting a space between the two chords, i.e. [ ] [A*] instead of [ ][A*]
3) Using just spaces instead of an empty chord, i.e. day by day?    [A*]

I understand you not wanting to have to modify your files though, and MobileSheets is behaving differently than the ChordPro application, so I'll see what I can do.

Mike

[Zubersoft]

I have this bug fixed for the next update.

Mike

[ARS]

I have this bug fixed for the next update.

Mike

Awesome!

Thank you