Thanks, but unfortunately that link refers to restoring a login after hibernation on FM Go 1.1. My question relates to when one force quits an app by flicking it upwards in the app switcher interface on latest version of FM Go.
My biggest concern is to try and overcome the problem where the restored state contains an empty found set which is ugly & confusing for users. As I've taken away the toolbar, the users don't have the capacity to adjust the found set.
Thank you for your posts.
After force quitting FileMaker Go, if you try to start FileMaker Go within 10 seconds, it will return to where you left off, even if you have fmreauthenticate0 extended privilege active for that user account. For more information, see page 21 of the FileMaker Go 13 Development Guide:
To avoid presenting the user with an empty found set, I'd modify the script to check for Get ( FoundCount ) = 0 and have the script take action to avoid this situation. Then no force quit is needed.
Thanks TSGal for reassurance that this is intentional behaviour and that there's no security issue as it respects the fmreauthenticate settings albeit with a 10 second grace period.
Regarding PhilModJunk's advice on a graceful refresh after returning from a force quit: There's no script trigger "OnOpenAfterForceQuit" which could be used to restore found set that applied before the crash/force-quit action. I'm going to go ahead and build a sample file that demonstrates this behaviour. Once I've got it ready I'll share it out.
There's no script trigger "OnOpenAfterForceQuit"
True, but you wouldn't want your users to see this under any circumstances when opening the file and you can thus use OnFirstWindowOpen to perform a script that checks the found set.
Darn, and I'm forgetting that this trigger won't be tripped either in this situation....