So, I just need a single click after locating the line whereas in Qt Creator I need to first right click and then pick the correct menu entry and left click.

Point taken, so a little QoL issue :) Use/assign a keyboard shortcut and you are down to one click (or move cursor to line with arrow keys) and one keypress :)

You have to indicate somehow for both "Run to line" & "Jump to line" which line you want it to continue to!

You are right. VS shows a little icon on the line you are currently hovering with the mouse. So, I just need a single click after locating the line whereas in Qt Creator I need to first right click and then pick the correct menu entry and left click. While I'm debugging I want as little friction as possible so as to not loose the context of what is going on.

@aha_1980 said in What is a better IDE for QT:

Run to line has the shortcut Ctrl+F10 ;)

I'm gonna remember this and probably use it the next time I have a smaller program which I can debug in Qt Creator.

If you want to stick with keyboard you can move the cursor there and press as @aha_1980 has said (existing shortcut) or add your own key if you want one for Jump to line, which is less common.

Run to line has the shortcut Ctrl+F10 ;)

Otherwise there is also Run to line XXX, so you can either run to a line or skip everything up to a line with a single click and no breakpoint add/remove?

Alright, I didn't know about this one. But, in this respect VS is still better because it is not hidden in a context menu ;-). It's already bad enough that I need to switch from my beloved keyboard to the mouse. An extra click is just too much... (This is slightly tongue in cheek–don't take it too seriously.)

sudo echo "You funny :)"

QtCreator is buggy beyond imagination. Visual Studio Code needs some more setup, but long term is worth of try

[cmake] CMake Error: Error: generator : Ninja
[cmake] Does not match the generator used previously: Ninja
[cmake] Either remove the CMakeCache.txt file and CMakeFiles directory or choose a different binary directory.

.... The second generator may have an extra space? :-o

• Run to line: Sets a temporary breakpoint on the line and stops when the program reaches this breakpoint
• Jump to ĺine: Sets the program counter to this line, skipping all instructions that are between the current program counter and the target. Use that with cause, because it changes the program flow and can have any possible side effects.

Regards

One additional advantage of VS over Qt Creator for debugging is that I can just skip to a certain line by just clicking there without having to set a breakpoint (and then immediately removing it afterwards). This is really helpful for jumping over loops. Other IDEs also have this feature.

Right-click in "breakpoint" gutter/margin to left of your code, on context menu only (no shortcut assigned) there is Jump to line XXX, which I assume is what you mean? Otherwise there is also Run to line XXX, so you can either run to a line or skip everything up to a line with a single click and no breakpoint add/remove? Both of these available in Creator as in VS.

One additional advantage of VS over Qt Creator for debugging is that I can just skip to a certain line by just clicking there without having to set a breakpoint (and then immediately removing it afterwards). This is really helpful for jumping over loops. Other IDEs also have this feature.

For debugging I am always switching over to Visual Studio. The debugging environment within Qt Creator is too slow for larger projects.

Could you say a few words about this, please? Why would Creator be any slower than VS? I thought Creator just provides a visual wrapper over the underlying debugger facilities? I am Linux/gdb, do you think your comment applies only under Windows Creator vs VS?

Did you add external libs with debug build?

Yes.

For debugging I am always switching over to Visual Studio. The debugging environment within Qt Creator is too slow for larger projects.

Especially with CMake-base projects you can also use Visual Studio Code. I have also tried CLion (now free for private projects). CLion is really nice and its debugging interface also works quite well (though I haven't used CLion for debugging on Windows, yet).

You can also use WinDbg independent of any IDE. This even provides time travel debugging. But, I think it is a lot harder to work with.

External libraries don't bring additional difficulties to me.

For example, I could not run Qwt on debug mode, because like that :

What I actually wanted to ask was this: Which IDE is more professional for using/adding external libraries and debugging? Which one would be more performant and meaningful for me? As you know, Visual Studio has a different project structure; does this hinder project development or sharing? I need answers to these questions. Which one is used more by percentage? Why do people prefer that IDE? I'm curious about these things. Sorry for the inconvenience.

I've been using Qt Creator professionally for more than a decade and it does the job for me.
External libraries don't bring additional difficulties to me.