[maks261]

(Note to Mike: i have collected a few feature ideas in the previous months, hence the multiple new topics opened by me, i hope it is okay that i kept one feature idea per forum thread)

First of all, there probably is some technical reason / limitation behind the fact, that MSP currently does not support it, so maybe you will enlighten me quickly and therefore render my feature request useless, Mike

For a long time i have been wondering, why a .cho-File and other files cannot coexist within a single song.

For me personally this is one of the most crucial missing features, because not only do all my songs use .cho files, but also do many of them have interesting intro riffs or whatever, that i would like to add in a separate pdf file or image file etc. - such that when i forgot the details i can quickly check them.

For now i am always adding guitar riffs etc. with the chordpro guitar directive at the beginning of songs, but it also comes with some downsides (like the width issue on small screens or the editing issue on companion, etc. - as mentioned in other forum threads).

It would be so handy to just add images, pdfs, etc. to an existing song which already uses a .cho file - that feature would be quite a game changer for me.

Btw, I used google to search your forum for existing topics and could not really find any, however i found someone asking about "song versions" ( https://www.zubersoft.com/mobilesheets/f...10596.html ) which might indeed be related solution wise. I could imagine having multiple song versions within a song (could be multiple .cho files, pdf files, whatever), and one of them then could be the file holding the complex guitar intro i mentioned, for example.

[sciurius]

ChordPro already supports including images in .cho files, and no doubt MobileSheets will add that in a future version.

[BRX]

Not to mention all the ABC stuff you can use to depict riffs and such.

[Zubersoft]

I'm adding image support with the next update (it's already implemented, I'm just about to start testing all the different options). 

maks261 - The main reason I didn't support it at the moment is due to the dynamic nature of ChordPro and text files. They don't have a predefined number of pages, and the number of pages can change drastically depending on changes to the text display settings. Many of the features in MobileSheets are tied to the page of a song (not to the page of a file). For example, if you place link points, bookmarks, annotations, etc, they are tied to the song page, which may or may not be the same as the file page. So if a link point is tied to page 3 of a song using a ChordPro file, then you decreased the text display settings so that now there is only one page, what should happen to that link point? At the moment, nothing happens to it - it's just not displayed, and if change the text display settings back so that there are three pages again, the link point would show up like you would expect. Now let's assume there is a PDF after the ChordPro file. Now what should I do? Should I delete the link point? Should I incorrectly show it on the PDF? There is nothing in the code that ties it to the ChordPro file, so MobileSheets does not know which file it should be associated with. Could I rewire all the code to use file pages instead of song pages? Yes, but it would require significant changes. The "file page" in this instance would still have to be in terms of the page ordering, because users can remove pages, duplicate pages, etc, and have different elements (annotations, bookmarks, link points, etc) on different instances of a page. So I would need to go through the entire database and change things so that everything is tied to the page of a particular file (and add a reference to the database file ID), and then change all of the code everywhere that uses song pages to instead map that to file pages before accessing things like link points, annotations, etc. I would also then have to rework all of the code that tries to figure out how to correctly handle changes to page orders. However, once all this work is done, some things would actually get simpler, and then I could support dynamic file types at the same time as files with a fixed number of pages. So it's probably something I will do long term, maybe when I tackle the song versioning changes, but it's definitely not something I want to tackle in the short term due to the huge amount of code changes this will result in (and the potential for bugs).

Mike