Hi Nicola!
Unfortunately there are naming collisions if an item exists in both Felgo and the Quick Controls 2 module. As you correctly suggested, that is the case for the Felgo and Qt Quick 2 Page item.
There are two solutions to this problem:
- As Alex mentioned above, you can use a dedicated identifier for an import. For example, when importing Quick Controls 2, use them like this:
import Felgo 3.0
import QtQuick.Controls 2.0 as Quick2
// Felgo Page (no special identifier required)
Page {
// Quick Controls 2 Tumbler (local namespace Quick2)
Quick2.Tumbler {
// ...
}
// ...
}
- The second option would be to create a custom control that only uses one of the imports, and use this control within Felgo then:
MyTumbler.qml:
import QtQuick.Controls 2.0
Tumbler { ... } // custom quick controls 2 tumbler, or at least only a wrapper to avoid the import in other files
VPlayPage.qml:
import Felgo 3.0
import "mycontrols" // myTumbler location
Page {
MyTumbler { ... } // add quick 2 tumbler
}
Best,
Günther