touch-packages team mailing list archive

[Sebastien Bacher <seb128@xxxxxxxxxx>]

right, so looking a bit more into the issue

the state saver code is

http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-
toolkit/trunk/view/head:/src/Ubuntu/Components/plugin/statesaverbackend_p.cpp#L44

only sig2/15 are handled by unix handlers, the state saver triggers on sigkill (which Didier is using for testing) through the 
"    QObject::connect(&QuickUtils::instance(), &QuickUtils::deactivated," signal

summary of the issues
- is sigkill supposed to be handled directly like e.g sigint?
- ContentStore somehow makes the "deactivated" signal stop being triggered
- the documentation doesn't list the handled signals

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to content-hub in Ubuntu.
https://bugs.launchpad.net/bugs/1485222

Title:
  Using ContentStore disables silently any StateSaver capability

Status in content-hub package in Ubuntu:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  1. Create the default template project
  2. Add on the page (with an id):
              TextField {
                  id: foo
                  StateSaver.properties: "text"
              }
  3. run the app, type something in the field, xkill it, restart
  -> the TextField content is restored by the StateSaver.
  4. import Ubuntu.Content 1.1
  -> StateSaver still works
  5. add anywhere on the page:
  ContentStore {
              id: appContentStore
              scope: ContentScope.App
          }
  -> The state is not restored anymore (note that it may be the first time, restoring when there was no ContentStore at kill time), then it constantly fails to restore.

  There is no warning or anything that reported an issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/content-hub/+bug/1485222/+subscriptions