A lot of warnings when adding Content Hub simple example

Bug #1483554 reported by Didier Roche-Tolomelli
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
content-hub (Ubuntu)
New
Undecided
Unassigned

Bug Description

I just added with Ubuntu Content 1.1 a simple example, here is the commit: https://github.com/didrocks/splitthebill/commit/bc914de9511ebbd3b13b03166bdc7c463af1c609

Switching that one, I'm starting to get a lot of warnings in my application related to contenthub. This is all at instantation, so before starting any transfer. The default experience shouldn't give any warning:

1. qml: WARNING: Header is an internal component of Ubuntu.Components andits API may change or be removed at any moment.Please use MainView and Page instead.

2. the activeTransfer is null by default, so the Connections will fail in: file:///<…>: Unable to assign [undefined] to QObject*

Maybe we should set a default value to activeTransfer? Or any other idea?

3. file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Content/ContentPeerPicker11.qml:204: TypeError: Cannot read property 'peers' of null

I guess that's because something isn't instantiated.

4. Once the peer in peerpicker is chosen, then transferHint triggers some warnigns:
file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Content/ContentTransferHint.qml:61:13: QML Button: Theme.createStyleComponent() is deprecated. Use ThemeSettings instead.
file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Content/ContentTransferHint.qml:54:13: QML ActivityIndicator: Theme.createStyleComponent() is deprecated. Use ThemeSettings instead.

(this is using Components 1.2)

5. hfile:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/Popups/1.2/Dialog.qml:179:13: QML Column: Cannot specify top, bottom, verticalCenter, fill or centerIn anchors for items inside Column. Column will not function.

Tags: devexp
description: updated
no longer affects: content-hub (Ubuntu)
affects: content-hub → content-hub (Ubuntu)
Revision history for this message
Ken VanDine (ken-vandine) wrote :

The warnings mentioned in numbers 4 and 5 are all internal to the SDK. If we update to 1.3 of the SDK those will go away, but we aren't ready to do that yet. Apps shouldn't have mixed imports for the SDK components, we'll need to provide a version of our components that import 1.3 from the SDK for apps that use 1.3.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.