[Zubersoft]

An "Offline Mode" for the companion is something people have asked for in the past (you can probably find the forum post if you want to view the history). At the moment, the design of the companion app does not support this at all. Every action that is taken in the companion is followed by the companion sending over the entire database file to the tablet. The reason this is done is so that I don't have to support sending across every database action that has to occur on the tablet, as that would greatly complicate a number of sections of my code and would increase the risk that the database may be partially modified when a disconnect occurs (which could be avoided if I wrapped everything in transactions). In order to support an offline mode, I would need to basically cache every change that needs to occur in the companion app and then send those changes over to the tablet when it gets connected later. The problem is that many of things in the app require information from the tablet in order to be correctly set up. For example, the MobileSheetsPro storage location must be read off the tablet so that all of the database paths can be correctly set up. Supporting this mode of caching all actions to be processed later is a huge deviation from my current approach, and would require separate branches of code at each point where a message is normally sent to the tablet. At sections where information is normally required from the tablet (such as editing songs where the preview is only available after the file is sent over from the tablet), I would also have to add extra conditions for the offline mode.

Supporting this is certainly something I want to do, but it's going to take a great deal of effort, and I'm not sure the benefit is great enough at this point in time with all of the other high priority work that has to be completed.

Mike