[Touch-packages] [Bug 1485222] Re: Using ContentStore disables silently any StateSaver capability

2015-10-19 Thread Pat McGowan 
** Changed in: canonical-devices-system-image
   Status: Fix Committed => Fix Released

-- 
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 Canonical System Image:
  Fix Released
Status in content-hub package in Ubuntu:
  Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid

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/canonical-devices-system-image/+bug/1485222/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1485222] Re: Using ContentStore disables silently any StateSaver capability

2015-09-02 Thread Bill Filler 
** Changed in: canonical-devices-system-image
   Status: New => Fix Committed

-- 
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 Canonical System Image:
  Fix Committed
Status in content-hub package in Ubuntu:
  Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid

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/canonical-devices-system-image/+bug/1485222/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1485222] Re: Using ContentStore disables silently any StateSaver capability

2015-08-31 Thread Launchpad Bug Tracker 
This bug was fixed in the package content-hub -
0.0+15.10.20150821.2-0ubuntu1

---
content-hub (0.0+15.10.20150821.2-0ubuntu1) wily; urgency=medium

  [ Ken VanDine ]
  * Don't swallow QEvent::ApplicationDeactivate (LP: #1485222)
  * added hasPending property on ContentHub (LP: #1487073)
  * generate plugins.qmltypes (LP: #1483626)

 -- CI Train Bot   Fri, 21 Aug 2015 16:36:06
+

** Changed in: content-hub (Ubuntu)
   Status: In Progress => Fix Released

-- 
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 Canonical System Image:
  New
Status in content-hub package in Ubuntu:
  Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid

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/canonical-devices-system-image/+bug/1485222/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1485222] Re: Using ContentStore disables silently any StateSaver capability

2015-08-28 Thread Launchpad Bug Tracker 
** Branch linked: lp:ubuntu/wily-proposed/content-hub

-- 
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 Canonical System Image:
  New
Status in content-hub package in Ubuntu:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid

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/canonical-devices-system-image/+bug/1485222/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1485222] Re: Using ContentStore disables silently any StateSaver capability

2015-08-23 Thread Bill Filler 
** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Changed in: canonical-devices-system-image
Milestone: None = ww40-2015

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) = Bill Filler (bfiller)

** Changed in: canonical-devices-system-image
   Importance: Undecided = High

-- 
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 Canonical System Image:
  New
Status in content-hub package in Ubuntu:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid

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/canonical-devices-system-image/+bug/1485222/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1485222] Re: Using ContentStore disables silently any StateSaver capability

2015-08-21 Thread Sebastien Bacher 
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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1485222] Re: Using ContentStore disables silently any StateSaver capability

2015-08-21 Thread Ken VanDine 
** Branch linked: lp:~ken-vandine/content-hub/dont_swallow_deactivate

-- 
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:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1485222] Re: Using ContentStore disables silently any StateSaver capability

2015-08-21 Thread Sebastien Bacher 
** Changed in: content-hub (Ubuntu)
   Importance: Undecided = High

** Changed in: content-hub (Ubuntu)
   Status: New = In Progress

** Changed in: content-hub (Ubuntu)
 Assignee: (unassigned) = Ken VanDine (ken-vandine)

-- 
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:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1485222] Re: Using ContentStore disables silently any StateSaver capability

2015-08-21 Thread Sebastien Bacher 
** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New = Invalid

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided = High

-- 
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:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1485222] Re: Using ContentStore disables silently any StateSaver capability

2015-08-21 Thread Zsombor Egri 
Does the ContentStore somehow alter APP_ID or applicationName? If it
does, StateSaver won;t find the state feel anymore.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1485222] Re: Using ContentStore disables silently any StateSaver capability

2015-08-21 Thread Zsombor Egri 
Ehh, typos, what I wanted to say is that it won't find the state file
anymore.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1485222] Re: Using ContentStore disables silently any StateSaver capability

2015-08-20 Thread Didier Roche 
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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1485222] Re: Using ContentStore disables silently any StateSaver capability

2015-08-20 Thread Zsombor Egri 
The logic to delay StateSaver when URI handler is installed did not land
in toolkit, so I wonder why it does disable the statesaver...

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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1485222] Re: Using ContentStore disables silently any StateSaver capability

2015-08-20 Thread Ken VanDine 
I can't see any way it could cause a problem with StateSaver.  The
ContentStore type is just a simple object with a couple of properties,
no functionality of it's own.  I really can't see any way it could be
related.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1485222] Re: Using ContentStore disables silently any StateSaver capability

2015-08-20 Thread Didier Roche 
** Also affects: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided
   Status: New

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1485222] Re: Using ContentStore disables silently any StateSaver capability

2015-08-16 Thread Didier Roche 
** Tags added: devexp

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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp