StateSaver discards the saved states on SIGTERM. This has been agreed long ago
when we stabilised the StateSaver requirements:
- states are saved every time the app goes background (inactive)
- SIGINT keeps the states saved
- SIGTERM, quit() clears the state data, as well as when the app comes
The app should've saved all volatile data when it went inactive, since
that's when there's no guarantee it will ever get resumed again.
The SIGTERM would just be a way to tell the app The user closed you,
clear yourself up as needed. Often it will be NOOP, assuming the app
uses StateSaver, which
What about the unsaved data case when an app is killed by life cycle
management? It seems problematic to me to lead app developers into
believing that users will see that question, when most of the time they
won't.
--
You received this bug notification because you are a member of Ubuntu
Touch
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Status: New = Confirmed
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Importance: Undecided = Medium
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Assignee: (unassigned) = Zsombor Egri (zsombi)
--
You received this bug notification because you
4 matches
Mail list logo
