I've checked the test with staging, and I get warnings for 0.1, 1.0, 1.1
and 1.2 imports. So seems staging has some fix which makes the warning
to be printed everywhere but 1.3.

About the logs, staging (and I think overlay PPA will get it soon) has
more info on where the problem relies. I am getting the following log:
"test.qml:5:5: QML Button: Theme.createStyleComponent() is deprecated.
Use ThemeSettings instead."

Theme is a context property. Context properties and Singletons are
impossible to know from which QML file are invoked. So we cannot really
display any meaningful information on where the component is used. We
cannot know whether the functionality is called from a toolkit component
or from an application or custom component based on toolkit. As seen
above, the staging which is also planned to be released, has more
information on Theme.createStyleComponent(), but that is the only one
can give valuable information. Theme.palette or Theme.name will not know
the caller context, and will not be able to specify from what document
it is addressed.

** Changed in: ubuntu-ui-toolkit (Ubuntu)
       Status: Confirmed => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1457528

Title:
  Theme.createStyleComponent deprecation useless warnings are displayed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1457528/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to