I agree. It's also _very_ confusing to newbies, that you can't always trust this mechanism. You've got to know better than the IDE. And you've got to know when you know better than the IDE.
Sent: Friday, November 09, 2018 at 1:00 PM
From: ekke <e...@ekkes-corner.org>
To: "qt-creator@qt-project.org" <qt-creator@qt-project.org>
Subject: [Qt-creator] it's a pain: QML Import Path not found and auto-completion broken working w multi projects / multi kits
From: ekke <e...@ekkes-corner.org>
To: "qt-creator@qt-project.org" <qt-creator@qt-project.org>
Subject: [Qt-creator] it's a pain: QML Import Path not found and auto-completion broken working w multi projects / multi kits
QtCreator gets so many cool new features, but daily work is a real pain, if
- working with some projects using different Kits (Android, iOS, Desktop) and have different selected
- having same ClassNames and context properties in multi projects
have created two videos to demonstrate this:
QML Import Path not found:
The First One Wins: auto-completion broken:
Both bugs break code-completion: the first one for all imports not found, second one for all but the first project accessing context properties with sdame name in different projects
this slows down productivity
ekke
_______________________________________________ Qt-creator mailing list Qt-creator@qt-project.org http://lists.qt-project.org/mailman/listinfo/qt-creator_______________________________________________ Qt-creator mailing list Qt-creator@qt-project.org http://lists.qt-project.org/mailman/listinfo/qt-creator
