UbuntuColors is the only "singleton" defined in a qmldir file as part of
Ubuntu.Components, so my hunch is that qmlplugindump can't handle that.

We could probably try and register it from C++ to see if that'd fix it.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1583985

Title:
  qmlplugindump for any module importing Ubuntu.Components always
  exposes UbuntuColors

Status in qtdeclarative-opensource-src package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  Not sure whether that’s a bug in the qmlplugindump tool itself, or in the 
UITK.
  When invoking qmlplugindump on any module that imports Ubuntu.Components, the 
resulting typeinfo always exposes the UbuntuColors component:

      Component {
          prototype: "QObject"
          name: "UbuntuColors"
          exports: ["UbuntuColors 1.3"]
          exportMetaObjectRevisions: [3]
          isComposite: true
          isCreatable: false
          isSingleton: true
          Property { name: "lightAubergine"; type: "QColor"; isReadonly: true }
          Property { name: "midAubergine"; type: "QColor"; isReadonly: true }
          Property { name: "darkAubergine"; type: "QColor"; isReadonly: true }
          Property { name: "warmGrey"; type: "QColor"; isReadonly: true }
          Property { name: "coolGrey"; type: "QColor"; isReadonly: true }
          Property { name: "orangeGradient"; type: "QQuickGradient"; isPointer: 
true }
          Property { name: "greyGradient"; type: "QQuickGradient"; isPointer: 
true }
          Property { name: "orange"; type: "QColor"; isReadonly: true }
          Property { name: "lightGrey"; type: "QColor"; isReadonly: true }
          Property { name: "silk"; type: "QColor"; isReadonly: true }
          Property { name: "darkGrey"; type: "QColor"; isReadonly: true }
          Property { name: "slate"; type: "QColor"; isReadonly: true }
          Property { name: "red"; type: "QColor"; isReadonly: true }
          Property { name: "green"; type: "QColor"; isReadonly: true }
          Property { name: "blue"; type: "QColor"; isReadonly: true }
          Property { name: "purple"; type: "QColor"; isReadonly: true }
          Property { name: "porcelain"; type: "QColor"; isReadonly: true }
          Property { name: "ash"; type: "QColor"; isReadonly: true }
          Property { name: "graphite"; type: "QColor"; isReadonly: true }
          Property { name: "inkstone"; type: "QColor"; isReadonly: true }
          Property { name: "jet"; type: "QColor"; isReadonly: true }
      }

  This can be easily reproduced by invoking e.g.:

      qmlplugindump -v -noinstantiate Ubuntu.Web 0.2 > test.qmltypes

  I’ve seen the same happen when dumping the qml types for
  Ubuntu.UnityWebApps (see https://code.launchpad.net/~osomon/unity-
  webapps-qml/qmltypes/+merge/295242).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1583985/+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

Reply via email to