More related bugs:
https://bugreports.qt.io/browse/QTBUG-50990
https://bugreports.qt.io/browse/QTBUG-48966
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1389721
Title:
API versioning broken in some
https://codereview.qt-project.org/#/c/146588/ is now merged to Qt 5.6.
** Also affects: qtdeclarative-opensource-src (Ubuntu RTM)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: qtdeclarative-opensource-src (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
Thanks, /me blind and blaming DST. Thanks for commenting more on the
upstream report, maybe it gets a bit of visibility.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1389721
Title:
API versioning b
+Timo, the bug is in Chris' comment #2. I'll add to the description.
** Description changed:
With Oxide 1.2 being the version that's shipping in the RTM image, I
want to start correctly versioning new API's so that we can upgrade
Oxide OTA safely without breaking existing applications. I'm
+Chris, so to give more help, the workaround:
1) create a new class which derives from the one you want to expose the
revisioned API
2) move all your revisioned API into this one
3) register the new class to the version you need with the same name as in the
previous version
>From the upstream bu
Could you bring the problem to upstream's attention via
https://bugreports.qt.io/ ? I tried to search for existing similar bug
reports but didn't find one. Possibly some better keyword would help in
searching though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
Actually we have revisions and we use the same declaration for
components in UI Toolkit as well. And the revisioning of ViewItems
attached properties are also broken, see
https://code.launchpad.net/~zsombi/ubuntu-ui-toolkit/listitem-
expansion/+merge/254375, where I had to do an ugly workaround to
Not exactly - the "1" matches the revision number specified in the
metadata in the class declarations. Eg,
--- qt/quick/api/oxideqquickwebcontext_p.h 2014-10-09 20:22:21 +
+++ qt/quick/api/oxideqquickwebcontext_p.h 2014-11-05 00:22:04 +
@@ -60,9 +60,9 @@
Q_PROPERTY(OxideQQui
I notice
+qmlRegisterType(uri, 1, 3, "WebContext");
the template argument passing the revision there - in the UITK we have
versioning but we don't use that one. Also, shouldn't it be 3?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
** Description changed:
With Oxide 1.2 being the version that's shipping in the RTM image, I
want to start correctly versioning new API's so that we can upgrade
Oxide OTA safely without breaking existing applications. I'm testing the
attached patch for Oxide to add a revision to API's that
This sounds similar to https://bugreports.qt-
project.org/browse/QTBUG-40043
** Description changed:
With Oxide 1.2 being the version that's shipping in the RTM image, I
want to start correctly versioning new API's so that we can upgrade
Oxide OTA safely without breaking existing applicatio
12 matches
Mail list logo
