[ghmerrill]

This is just weird ...

I just started up MobileSheets on my Windows tablet.  It had been working fine last night.  Apparently overnight there was an upgrade.

Everything seems to work fine EXCEPT ...

1. MobileSheets now seems to want to come up in full screen no matter whether I resize it and then exit it or not.

2. I have a collection that is just a list of PDF documents, including some exercise books in PDF format.  Exactly ONE of those now fails to load when I click on it. Yesterday, prior to the upgrade, it loaded fine and was navigable, including the bookmarks.  Now when I click on it, it just goes shows the circular "working" icon and never terminates.  I've tried deleting and re-adding it.  I've tried reinstalling MobileSheets from the MS store.  Same story -- it won't load.  Everything else works fine.  The PDF is easily readable in any PDF reader I have, and it was readable since I initially added it to MobileSheets -- until today.

[Zubersoft]

1. That's controlled by Settings->Display Settings->Fullscreen Mode, and I did not change that behavior

2. I submitted an update yesterday to resolve this, but Microsoft complained about some of the keywords on the store page (even though they didn't complain about them for the last 7+ years). So I had to resubmit the update. Hopefully it will be resolved soon. You can go to Settings->Display Settings->Render Preference and switch to "Speed" if you need a workaround.

Mike

[ghmerrill]

Okay, I got those sorted out.  Rendering setting solves that loading problem.  I'm unclear on how the Fullscreen mode got changed.

In addition to that, I then noticed that the touch actions weren't working correctly (and scrolling actions weren't either).  When I restore a backup to the Windows system, it appears that default values are being used for these.  When I restore the same backup to my Chromebook, I see the expected settings and behavior for touch and scrolling.  The boxes for "Enable pinch zoom gesture", "Enable tap to turn pages", and "Enable swipe to turn pages" are also all checked in the Windows instances but unchecked in the Chromebook instance.

I have carefully done this twice, restoring from the SAME file on my Google Drive.  The Chromebook instance is restored correctly (with the expected Touch Action Settings) while the Windows instance is restored to (what appear to be) default values -- completely different.

I have even copied the backup file from my Google Drive to the local Windows drive and restored it from there.  Again, it does not restore the correct Touch Action Settings.

Any idea on how this could be happening?  Can I back out my Windows update to the earlier version and try that?

---------------------------------------------------

Ah, I see now that this is a long-standing known problem.  I just needed to find the right search phrase for it.  I suspect the Fullscreen Mode setting was a consequence of the same issue.  I've seem to have fixed it now in the most straightforward way and will know what to do in the future -- and will now probably take the added step as a precaution when saving/restoring in order to avoid any unwelcome surprises. 

[Zubersoft]

This definitely isn't a new problem, as I didn't change any code related to that. I'll run some tests with now with my own backups to see if I can reproduce that. Otherwise I'll need to get a copy of a backup file (or export the settings to .mcf) so I can see if I can reproduce it.

Thanks,
Mike

[ghmerrill]

Okay, let me know if you need that.  The workaround (which is essentially de-automating a step) works for me.  It was just really surprising to encounter it.  I'm not sure exporting the settings will show anything.

When I do the restore and then follow that with an import of the settings, it ends up like it should (as far as I can see).  And it happened literally overnight.  I'd been using the old version late last night.  Then this morning after I'd updated (because I'd noticed that my Chrome version had updated), I ran straight into it -- at least that's my recollection.  The first sign was the display failure of that one PDF file, and then when I'd gotten around that via your suggestion, other things seemed to be revealed from there.  It's as though the database restore process ignores the settings and silently imposes the default ones.  But the Import Settings function appears to work.  And of course the ChromeOS (Android) version doesn't appear to even burp on the database restore.

[Zubersoft]

I can't reproduce an issue. I restored a backup from Android and the touch settings you mention were correctly transferred. If you want to share the backup file with me, I can take a look at what is happening on Windows with your backup.

Thanks,
Mike