touch-packages team mailing list archive

[Didier Roche <didrocks@xxxxxxxxxx>]

10:42:55     zsombi | [11:25:35] <zsombi> didrocks: if a simple ContentStore disables StateSaver, then perhabs that should be checked 
                    | fiorst...                                                                                                       
10:42:55     zsombi | [11:26:19] <zsombi> didrocks: all StateSaver does is to hook to SIGINT and SIGTERM signals to get notified when 
                    | the app is killed/stopped, not more                                                                             
10:42:55     zsombi | [11:26:53] <zsombi> didrocks: and then, if there're states saved, it will restore them one by one as they come  
                    | alive                                                                                                           
10:42:55     zsombi | [11:28:30] <zsombi> didrocks: there is a piece of code to which kenvandine might refer, which arises when an app
                    | is launched thru ContentHub, which delays state restoration till the URI is handled, but that piece of code is  
                    | not in the toolkit, so these two components have nothing in common really                                       

Ken, seems that Zomber thinks it's on your side, mind looking at it
then? Thanks!

-- 
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