Qt Creator Rant
-
Everytime there is some weird thing going on in my code, i know somehow, somewhere along the way Qt Creator fucked up.
If anything weird happens the first thing i do is to to delete my whole build folder. Most of the time that solves the problem.
Recently I changed my pro file. I wanted to delete CONFIG += console and add CONFIG -= console. Saved it, it said it saved it, i hit build and ... it build too fast. Turns out that it didnt recompile my code, as i see from the creation time. So i had to add a whitespace, then delete it inside an cpp file to make it take my change.
Things like these cost me production time. And thats just one example of many.
-
Wouldn't it be better to report good bug reports so the issues get fixed instead writing something to a user forum where just with some luck the developers will see your issue?
-
After editing anything in the pro file it's often required to re-run qmake manually for any change to be noticed (Build -> Run qmake). This shouldn't work like that of course. It's been reported and claimed to be fixed many many times, but it's still the case and personally I just learned to live with it. I assigned a shortcut to it, so whenever I edit pro file I hit save and rerun qmake shortcuts. It takes one extra keystroke and it became muscle memory for me, so I don't even think about it anymore.
But yeah, if you have a repro example report a bug. Maybe one day it'll be fixed for good, but as Christian said complaining here on the forum won't do you any good.
