ITEM COULD NOT BE CREATED
-
I am facing the same issue on both my PC and Mac when using the QtCreator 5.0.0 and Qt 6.1 or 6.2 beta kits with new/old QtQuick Projects. The issue is not present when I'm working with Qt 5.15.2. Adding or removing version numbers does not have an effect on the issue. My PC is i9-10850K and GTX970 running Windows 10, and my Mac is Macbook Air M1 base model. Everything else works, including build, running on real devices / simulators, etc.
-
@arewethereyet said in ITEM COULD NOT BE CREATED:
I am facing the same issue on both my PC and Mac when using the QtCreator 5.0.0 and Qt 6.1 or 6.2 beta kits with new/old QtQuick Projects. The issue is not present when I'm working with Qt 5.15.2. Adding or removing version numbers does not have an effect on the issue. My PC is i9-10850K and GTX970 running Windows 10, and my Mac is Macbook Air M1 base model. Everything else works, including build, running on real devices / simulators, etc.
I tested Qt 6.1.3 GCC kit on Zorin OS (based on Ubuntu 20.04.3 LTS) and the problem is present there as well. Is there any solution to this problem or what could be causing it? There's no Felgo hot reload for Qt 6 yet to my understanding, so I cannot use that to bypass design view issues when developing front-end either...
-
I'm also experiencing this issue using QtCreator 5.0.0 and QT version 6.1.3 on macOS Big Sur (11.5.2). When starting a new project with the base qml window code, I can run the project and the window will appear. Switching to the Design view, I am unable to see the form in the form editor, and in the Navigator pane, hovering over the "Window" component displays the message: "item could not be created."
-
Popping in to say that I am experiencing this issue when I create a new project in QT Creator with the Qt 6.0 minimal version selection.
-
Having the same issue with Qt Creator 5.0.1, Qt 6.1.3 MinGW 64-bit on Windows 10 64bit.
All items in the Navigator panel have a warning sign next to them, are underlined in red and their tooltip says 'Item could not be created'.
Running the application works like a charm, but the preview in the Form Editor doesn't work. -
@sbentzien same configuration and the same issue here
-
Is anyone aware of how to escalate this with the QTCreator Dev/Support team? This seems like a painfully long time to have an issue like this, which is a software block, and not have been follow-up on by someone.
-
@John-Cordell Was this reported as bug in Qt bug tracker?
-
Me too, 5.15 fine, 6.1.3 gets red squiggles under "window" in design view.
-
This work for me! QT 6.2.0
- Go to Tools > Options > QT Quick
- Inside QT QUICK DESIGNER TAB check the second options and copy/paste same path of first in secont
- Restart your QT and wait for build
OBS: Autocomplete dont work when import something like quick controls, so import without version or put 6.0
Enjoy!
-
@Nathan-Miguel I had tried this before with the 6.2 beta, and it didn't work, but now with "Top level build path" of the QML emulation layer set to "<Path To Qt>Qt/6.2.0/macOS/bin" worked for me, finally.
-
@Nathan-Miguel Working on the new 6.2 LTS with Creator 5.0. You are a champion thank you so much for the help.
-
@Nathan-Miguel Unfortunately that didn't help me as that seems to work only for desktop projects :|
For Android Kits I'm getting this error when trying your solution:
-
@Tahmis I think this should help
in steep 2 instead use this path try "<Path To Qt>/6.2.0/Kit android"
and try to see in MaintenanceTool if you don't have any pending updates and if you linked the android sdk in the QT options
-
@Nathan-Miguel No luck unfortunately.
Tried this now as you suggested and still getting the same error of which I pasted a screenshot earlier:
My QT installation is totally fresh and everything is updated and android sdk is linked in the options. I believe your workaround doesn't work for mobile kits :|
-
@Nathan-Miguel I think I tried that also earlier but tried again without success..
Thanks anyway!
Maybe Windows 11 upgrade surprisingly fixes something and it starts to work :D
-
@Nathan-Miguel thanks works for me!
-
it is so sad! when solve?
