On Tuesday, 19 March 2019 09:03:16 PDT Jason H wrote:
> I don't know why you can't just use a C/C++ preprocessor to generate the
> qml? For Clang, -E : Only run the preprocessor
qglobal.h is assembler-safe too. -D__ASSEMBLER__ and it won't produce C or C++
code that would confuse your parser.
> On 18/03/19 12:11, Pierre-Yves Siret wrote:
> > This can be done with QQmlFileSelector :
> >
> > QQmlApplicationEngine engine;
> > QQmlFileSelector* qmlFileSelector = QQmlFileSelector::get(&engine);
> >
> > #if QT_VERSION >= QT_VERSION_CHECK(5, 12, 0)
> > qmlFileSelector->setExtraSe
On 18/03/19 12:11, Pierre-Yves Siret wrote:
> This can be done with QQmlFileSelector :
>
> QQmlApplicationEngine engine;
> QQmlFileSelector* qmlFileSelector = QQmlFileSelector::get(&engine);
>
> #if QT_VERSION >= QT_VERSION_CHECK(5, 12, 0)
> qmlFileSelector->setExtraSelectors({"5.12"}
Am So., 17. März 2019 um 13:35 Uhr schrieb Alberto Mardegan
:
>
> Hi there!
> When developing a QML module for the greater public one wants to
> provide a source package that can be built on multiple Qt versions.
> However, QML's lack of a preprocessor makes this rather cumbersome.
>
> Suppose th
Hello,
This can be done with QQmlFileSelector :
QQmlApplicationEngine engine;
QQmlFileSelector* qmlFileSelector = QQmlFileSelector::get(&engine);
#if QT_VERSION >= QT_VERSION_CHECK(5, 12, 0)
qmlFileSelector->setExtraSelectors({"5.12"});
#endif
engine.load(QUrl(QStringLiteral("qr
El diumenge, 17 de març de 2019, a les 13:34:09 CET, Alberto Mardegan va
escriure:
> Hi there!
> When developing a QML module for the greater public one wants to
> provide a source package that can be built on multiple Qt versions.
> However, QML's lack of a preprocessor makes this rather cumber
Hi there!
When developing a QML module for the greater public one wants to
provide a source package that can be built on multiple Qt versions.
However, QML's lack of a preprocessor makes this rather cumbersome.
Suppose that my module needs to provide an element like this:
import QtQuick 2.
