Theme.createStyleComponent deprecation useless warnings are displayed
Bug #1457528 reported by
Sebastien Bacher
This bug affects 6 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical System Image |
Fix Released
|
High
|
Zoltan Balogh | ||
ubuntu-ui-toolkit (Ubuntu) |
Fix Released
|
High
|
Cris Dywan | ||
Vivid |
New
|
Undecided
|
Unassigned |
Bug Description
Take that example
"import QtQuick 2.0
import Ubuntu.Components 0.1
Item {
Button {
text: "click"
}
}"
run it on wily, you get those warnings
"QML Button: Theme.createSty
the warning is not helpful, it warns about a standard component issue (so something in the responsability of the uitk team, not the code writer), lists the issue on something you are not using (what is "Theme.
Related branches
lp://staging/~ubuntu-sdk-team/ubuntu-ui-toolkit/noDepNoteForComponents
- PS Jenkins bot: Approve (continuous-integration)
- Zsombor Egri: Approve
-
Diff: 26 lines (+9/-0)1 file modifiedmodules/Ubuntu/Components/plugin/ucdeprecatedtheme.cpp (+9/-0)
Changed in ubuntu-ui-toolkit (Ubuntu): | |
status: | New → Confirmed |
assignee: | nobody → Zsombor Egri (zsombi) |
Changed in ubuntu-ui-toolkit (Ubuntu): | |
status: | Fix Committed → Confirmed |
Changed in ubuntu-ui-toolkit (Ubuntu): | |
importance: | Undecided → High |
Changed in ubuntu-ui-toolkit (Ubuntu): | |
assignee: | Zsombor Egri (zsombi) → Christian Dywan (kalikiana) |
status: | Confirmed → In Progress |
Changed in ubuntu-ui-toolkit (Ubuntu): | |
status: | In Progress → Fix Committed |
Changed in canonical-devices-system-image: | |
milestone: | none → ww34-2015 |
assignee: | nobody → Zoltan Balogh (bzoltan) |
importance: | Undecided → High |
Changed in canonical-devices-system-image: | |
status: | New → Fix Committed |
Changed in canonical-devices-system-image: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
<seb128> timp, the warning goes away if you update the import version to e.g 1.1, so I guess that's what needs to be changed, but the warning hint is not helpful in this case
If updating the import version is supposed to fix the warning, we should say that in the printed message to help the app developers figure out what's wrong.