Hi Ulf
Thank you for the response. This setup generates a qmllint warning, even
in a skeleton QtCreator project. A bug report has been created:
https://bugreports.qt.io/browse/QTBUG-116623
Kind regards
Matthew
On 2023/08/30 15:58, Ulf Hermann via Interest wrote:
You can expose the type as b
You can expose the type as both a value type and a namespace:
struct TestGadget
{
Q_GADGET
QML_NAMED_ELEMENT(testGadget)
Q_PROPERTY(int value MEMBER value)
public:
enum class GadgetEnum
{
OptionA,
OptionB,
OptionC,
};
Q_ENUM(GadgetEnum)
};
str
Hi,
thanks a lot, it's working perfectly now :)
Le 30/08/2023 à 15:40, Alexandru Croitor a écrit :
Hi,
Instead of specifying the Qt6_DIR env var, pass
-DCMAKE_PREFIX_PATH=C:\Qt\6.6.0\msvc2019_64 to CMake.
Specifying the Qt6_DIR cache var is not sufficient to find Qt at the moment
(there is
Hi,
Instead of specifying the Qt6_DIR env var, pass
-DCMAKE_PREFIX_PATH=C:\Qt\6.6.0\msvc2019_64 to CMake.
Specifying the Qt6_DIR cache var is not sufficient to find Qt at the moment
(there is an open bug about it).
Specifying the Qt6_DIR env var not being sufficient is likely the same issue.
>
Hi,
Itm trying to build a project which use Qt on Windows with CMake.
I defined an env-variable Qt6_DIR to C:\Qt\6.6.0\msvc2019_64
I have the following error:
" Found package configuration file:
C:/Qt/6.6.0/msvc2019_64/lib/cmake/Qt6/Qt6Config.cmake
but it set Qt6_FOUND to FALSE so package
Hi Ulf
Thank you for your response.
-- QtLocation --
Thanks for catching this. See
https://codereview.qt-project.org/c/qt/qtlocation/+/500504 for a fix.
That's great, thank you.
-- 'as' operator --
This should work. Type assertions (aka "as cast") are documented in
https://doc.qt.io/qt-
Rule
of thumb is "one module: one directory, one CMakeLists.txt + uri must
follow source directory structure from project base". Im my experience
any derivation from that rule causes pain and suffering ;-) Or maybe I
still don't fully understand the IMPORTS, OPTIONAL_IMPORTS.
DEFAULT_IMPORTS, DEPE
Hi Matthew,
On Wed, Aug 30, 2023 at 7:50 AM Matthew Fincham via Interest
wrote:
> We are in the process of integrating qmllint after migrating a project to
> Qt6, and have hit a few issues.
> ...
> Please also note the type registration is done manually, not with the code
> generated by qmltype
Hi Matthew,
-- QtLocation --
The linter is unable to resolve types in QtLocation. Adding the
following dependencies to qml/QtLocation/qmldir resolved the problem:
depends QtQuick
depends QtPositioning
Thanks for catching this. See
https://codereview.qt-project.org/c/qt/qtlocation/+
