If there's more than one main item in the ScrollablePage, QtQuick gets
confused and the placeholder does not get displayed.
(cherry picked from commit e0a64f4a30)
To have the code bits reusable, they are defined as cmake variables.
In order to make the relative paths work and avoid touching every line
from the QRC, the resulting file is put into the source dir.
Summary: Now devices are shown same as in Android app, as in Kirigami app (kcapp)
Test Plan:
* Build kdeconnect, using the experimental version
* Try pairing, unpairing, connecting and disconnected devices.
* See the difference.
Reviewers: albertvaka, #kde_connect, nicolasfella
Reviewed By: #kde_connect, nicolasfella
Subscribers: nicolasfella, kdeconnect
Tags: #kde_connect
Differential Revision: https://phabricator.kde.org/D16935
Summary: There is no reason to disable it. On Android we do the same
Test Plan: Click on paired device in list, correct Page opens
Reviewers: #kde_connect, apol
Reviewed By: #kde_connect, apol
Subscribers: kdeconnect, #kde_connect
Tags: #kde_connect
Differential Revision: https://phabricator.kde.org/D13454
Summary: When a DevicePage is created from FindDevicePage the device is not passed correctly, resulting in some device is null warnings. The pair button still does not work, but it seems to be another issue.
Test Plan: I could set the button text to the device id, so the device is passed correctly. The button still does not work as intended though.
Reviewers: #kde_connect
Subscribers: apol, #kde_connect
Tags: #kde_connect
Differential Revision: https://phabricator.kde.org/D12506
