4 hours ago
Short answer - yes, it would be difficult due to how things are architected. You could just modify the page order to use all of the pages of the files, and then change it back to what it was after. Or you could create a copy of the song where you do that and then delete the extra song after. If I tried to support this in MobileSheets, I would effectively be doing the same thing - just resetting the page order. Doing that in a way where the original day is unaffected is challenging though. I would probably just create an internal copy of the song with its original state, modify the page order to use all pages (which will require modifying the database to ensure nothing gets broken with other features), allow the song to be viewed, and then have a way to reset it back to the saved state after. There are many issues with this approach though:
1) What happens if the app was closed without that saved instance being restored? If I have to persist the saved copy somewhere else in the database to prevent this data loss, things start getting a bit messy, as that would require data across many database tables.
2) What happens if the user modifies the song while viewing it in the temporary state that uses all pages? For example, if they start annotating those pages. Does that all then get deleted when it reverts? Is this what the user would expect?
Making it read-only in that state would require huge changes. Disabling features while its in that state would also require a huge number of changes. So no matter what, this would wind up being difficult and time-consuming to implement.
kimbered - embed the annotations in the annotations editor (tap the three dots at the top right corner and select "Embed annotations"). This will write the annotations into the PDF itself, and then any song using the PDF will show those annotations. The annotations won't be editable unless you also enable "Allow editing of embedded PDF annotations", but I wouldn't recommend leaving that setting on all the time as it breaks the seamless transition between viewing and annotating because the PDF has to be reloaded in an editable state (do to quirks with the PDF library I use).
Mike
1) What happens if the app was closed without that saved instance being restored? If I have to persist the saved copy somewhere else in the database to prevent this data loss, things start getting a bit messy, as that would require data across many database tables.
2) What happens if the user modifies the song while viewing it in the temporary state that uses all pages? For example, if they start annotating those pages. Does that all then get deleted when it reverts? Is this what the user would expect?
Making it read-only in that state would require huge changes. Disabling features while its in that state would also require a huge number of changes. So no matter what, this would wind up being difficult and time-consuming to implement.
kimbered - embed the annotations in the annotations editor (tap the three dots at the top right corner and select "Embed annotations"). This will write the annotations into the PDF itself, and then any song using the PDF will show those annotations. The annotations won't be editable unless you also enable "Allow editing of embedded PDF annotations", but I wouldn't recommend leaving that setting on all the time as it breaks the seamless transition between viewing and annotating because the PDF has to be reloaded in an editable state (do to quirks with the PDF library I use).
Mike