In case I have a line without lyrics, just chords, the position of the chords depends on the content of the next line. This should not be the case because the file is clearly in ChordPro syntax.
The same file rendered with ChordPro 6.060 shows that a font with 'real flats' as mentioned in another thread looks much better
While investigating that, I noticed that one of my computers behaves strangely: transposing of lowercase chords doesn't work, chord localization 'Scandinavian' is not working. The other one works as expected. Both run MobileSheets 3.9.7 on a current Win10. The only difference that I'm aware of: on the faulty one I skipped several MobileSheets versions and updated directly from 3.8.xx to 3.9.7.
Is it worth investigating that further? Or should I just try uninstalling and installing 3.9.7 from scratch?
That's incredibly strange... I do think uninstalling and reinstalling should hopefully fix it. Alternatively, you may need to just delete the default.xml settings file in the default storage location folder to reset the settings, as I'm wondering if that file is corrupted on that device.
I deleted default.xml. Now the MobileSheets Storage Location is lost and replaced by c:\Users\her\AppData\Local\Packages\41730Zubersoft.MobileSheets_ys1c8ct2g6ypr\LocalState\ - probably as expected.
I set it back to d:\HerbertsGoogleDrive\_MobileSheets\ as it was before and now MobileSheets shows a progress bar "Moving Files to New Location" which takes incredibly long - what's that? There should be nothing to move at all.
How about my main post, the strange chord positions?
MobileSheets always tries to move files when the storage location is changed. Unfortunately, it's problematic to reset the settings with a default storage location and then pick the new storage location. You can manually edit the default.xml file to specify the storage location and then pick the folder when prompted at startup to avoid this scenario.
10 hours ago(This post was last modified: 10 hours ago by Zubersoft.)
As far as the chords, MobileSheets recognizes that you have two lines of chords back to back, so it doesn't try to position the chords in the first chord line relative to anything. However, it then reads the second line of chords and sees that there are lyrics below it. So it's trying to line up those chords with the lyrics on the next line. This logic is somewhat borrowed from text files. I guess can just remove this logic with chord pro files and force users to display their chords normally instead of allowing them to be positioned on a separate line. We will see if I get any complaints after making this change.
(10 hours ago)Zubersoft Wrote: As far as the chords, MobileSheets recognizes that you have two lines of chords back to back, so it doesn't try to position the chords in the first chord line relative to anything. However, it then reads the second line of chords and sees that there are lyrics below it. So it's trying to line up those chords with the lyrics on the next line. This logic is somewhat borrowed from text files. I guess can just remove this logic with chord pro files and force users to display their chords normally instead of allowing them to be positioned on a separate line. We will see if I get any complaints after making this change.
Mike
That's what I assumed, that text file logic is applied. That's just wrong.
In ChordPro all information is within the current line, there's no dependency from or to the next or previous line.
Please fix that and in case somebody complains about it we just need to explain how it is intended to work.
(11 hours ago)Zubersoft Wrote: It's something I'm going to have to look into.
MobileSheets always tries to move files when the storage location is changed. Unfortunately, it's problematic to reset the settings with a default storage location and then pick the new storage location. You can manually edit the default.xml file to specify the storage location and then pick the folder when prompted at startup to avoid this scenario.
Mike
Why MobileSheets tries to move files that are not there is imho not worth investing effort, I assume it's a rare scenario and except taking time it doesn't do any harm.
More important:
Deleting default.xml did not change the behaviour. So I uninstalled MobileSheets and reinstalled it from the MicrosoftStore. After uninstalling LocalState was completely empty, I checked that. After reinstalling a new, empty mobilesheets.db had been created, so there was no issue with copying anything. I created a new msptest.db and imported EineReiseInsGlueck_F.pro as in my first post.
VERY STRANGE: transposing lowercase still doesn't work!
I have two computers pretending to run the same OS and the same MobileSheets version and they behave differently!
(11 hours ago)Zubersoft Wrote: It's something I'm going to have to look into.
MobileSheets always tries to move files when the storage location is changed. Unfortunately, it's problematic to reset the settings with a default storage location and then pick the new storage location. You can manually edit the default.xml file to specify the storage location and then pick the folder when prompted at startup to avoid this scenario.
Mike
Why MobileSheets tries to move files that are not there is imho not worth investing effort, I assume it's a rare scenario and except taking time it doesn't do any harm.
More important:
Deleting default.xml did not change the behaviour. So I uninstalled MobileSheets and reinstalled it from the MicrosoftStore. After uninstalling LocalState was completely empty, I checked that. After reinstalling a new, empty mobilesheets.db had been created, so there was no issue with copying anything. I created a new msptest.db and imported EineReiseInsGlueck_F.pro as in my first post.
VERY STRANGE: transposing lowercase still doesn't work!
I have two computers pretending to run the same OS and the same MobileSheets version and they behave differently!
Solved.
Text File Settings - Allow Lowercase Chords = ON was missing.
This is (quite logically) required for transposing and transcoding lowercase 'chords'.
