Annoying problem with Qt Creator software after update
-
had to upload the video -> https://streamable.com/oxeb11
here you can see what i mean in action it happens constantly
-
had to upload the video -> https://streamable.com/oxeb11
here you can see what i mean in action it happens constantly
@Kris-Revi The funny thing is that I had the same problem with QtCreator 14 on Ubuntu 22.04. But the same issue is gone in QtCreator 15 on Ubuntu 22.04. I am wondering if Qt developers have done enough testing before any releases.
-
@Kris-Revi The funny thing is that I had the same problem with QtCreator 14 on Ubuntu 22.04. But the same issue is gone in QtCreator 15 on Ubuntu 22.04. I am wondering if Qt developers have done enough testing before any releases.
-
had to upload the video -> https://streamable.com/oxeb11
here you can see what i mean in action it happens constantly
@Kris-Revi said in Annoying problem with Qt Creator software after update:
had to upload the video -> https://streamable.com/oxeb11
here you can see what i mean in action it happens constantly
Thank you for the video. I don't think this has anything to do with the licensing, you can forget about it.
The issue with licensing was that Qt Creator wouldn't start.
But this is a code completion issue. Some questions:
- How powerful is the computer that are using?
- Do you have
clangdenabled in Preferences > C++ > Clangd - Can you compile your project?
In the video we can see that the code model has some issues. The project is not correctly configured.
-
Computer specs
- MSI Z790-P PRO
- Intel Core i9-13900K
- DDR5, 5600MT/s 32GB 2x16GB DIMM
- ASUS DUAL GeForce RTX 4070 SUPER OC
so don't think that is the problem
Clangdis enabled
also i was able to build/compile my project just fine
(FIY the project i had loaded in the video was a faulty project i just loaded up quickly to show the cursor loading problem)
-
You could have a look at Tools > Debug Qt Creator > Show Logs ... for details. But I don't actually know what to tell you to watch after.
Here in my Windows VM the wait cursor doesn't appear. I do have the Windows antivirus with real-time protection enabled.
-
You could have a look at Tools > Debug Qt Creator > Show Logs ... for details. But I don't actually know what to tell you to watch after.
Here in my Windows VM the wait cursor doesn't appear. I do have the Windows antivirus with real-time protection enabled.
@cristian-adam so i got something out of looking into the debug logs
16:57:40.378 qtc.android.androiddevice.debug: Running command (sync): "C:\\Users\\krist\\AppData\\Local\\Android\\Sdk\\platform-tools\\adb.exe -s emulator-5562 emu avd name" 16:57:40.379 qtc.utils.process.debug: Process 3 starting (blocking with event loop, main thread): C:\Users\krist\AppData\Local\Android\Sdk\platform-tools\adb.exe -s emulator-5562 emu avd name 16:57:42.419 qtc.utils.process.debug: Process 3 finished: result=1, ex=1, 0 bytes stdout: "", 161 bytes stderr: "error: could not connect to TCP port 5562: cannot connect to 127.0.0.1:5562: No connection could be made because the target machine actively refused it. (10061)\n", 2040 ms elapsed 16:57:42.419 qtc.utils.process.stderr.debug: Process 3 stderr: "error: could not connect to TCP port 5562: cannot connect to 127.0.0.1:5562: No connection could be made because the target machine actively refused it. (10061)\n" 16:57:42.420 qtc.android.androiddevice.debug: Command finshed (sync): "C:\\Users\\krist\\AppData\\Local\\Android\\Sdk\\platform-tools\\adb.exe -s emulator-5562 emu avd name" Success: false Output: "error: could not connect to TCP port 5562: cannot connect to 127.0.0.1:5562: No connection could be made because the target machine actively refused it. (10061)\r\n" 16:57:50.387 qtc.android.androiddevice.debug: Running command (sync): "C:\\Users\\krist\\AppData\\Local\\Android\\Sdk\\platform-tools\\adb.exe -s emulator-5562 emu avd name" 16:57:50.388 qtc.utils.process.debug: Process 4 starting (blocking with event loop, main thread): C:\Users\krist\AppData\Local\Android\Sdk\platform-tools\adb.exe -s emulator-5562 emu avd name 16:57:52.465 qtc.utils.process.debug: Process 4 finished: result=1, ex=1, 0 bytes stdout: "", 161 bytes stderr: "error: could not connect to TCP port 5562: cannot connect to 127.0.0.1:5562: No connection could be made because the target machine actively refused it. (10061)\n", 2077 ms elapsed 16:57:52.465 qtc.utils.process.stderr.debug: Process 4 stderr: "error: could not connect to TCP port 5562: cannot connect to 127.0.0.1:5562: No connection could be made because the target machine actively refused it. (10061)\n" 16:57:52.465 qtc.android.androiddevice.debug: Command finshed (sync): "C:\\Users\\krist\\AppData\\Local\\Android\\Sdk\\platform-tools\\adb.exe -s emulator-5562 emu avd name" Success: false Output: "error: could not connect to TCP port 5562: cannot connect to 127.0.0.1:5562: No connection could be made because the target machine actively refused it. (10061)\r\n"something todo with
Running command (sync) -
You could have a look at Tools > Debug Qt Creator > Show Logs ... for details. But I don't actually know what to tell you to watch after.
Here in my Windows VM the wait cursor doesn't appear. I do have the Windows antivirus with real-time protection enabled.
@cristian-adam but what does it mean?
-
It looks like there is an issue with the Android plugin having issues connecting to the Emulator.
But I think this should not have any effect on the code completion...
-
It looks like there is an issue with the Android plugin having issues connecting to the Emulator.
But I think this should not have any effect on the code completion...
@cristian-adam but i don't use an emulator i have my Samsung Pad connected!
also this problem happens without me writing or doing anything inside Qt Creator so i don't think it is a "code completion" problem
-
At https://stackoverflow.com/questions/29826101/how-to-restart-adb-manually-from-android-studio we learn that one has to do a:
$ adb kill-server && adb start-serverYou could have this in a script that start Qt Creator, or in Qt Creator as an external tool.
