You're killing me Smalls! aka "qtRunWork task returned false but did not log an error"
-
This is ridiculous. My code base is large. Every once in a blue moon, I might bump a key right as I'm closing a file or maybe bump the wrong key as I hit a keyboard shortcut. And if there's a typo somewhere under my signals heading, suddenly it won't compile and gives me the error "qtRunWork task returned false but did not log an error". It doesn't tell me what file this is in or what line.
I have hundreds of files in this project, and having to go through all my header files to see which one of them might have a typo somewhere is unworkable. When qt sees an error, we need to know what file and what line. Please!!!!!
-
C Christian Ehrlicher moved this topic from General and Desktop on
-
Hi @GuitarMan,
I have hundreds of files in this project, and having to go through all my header files to see which one of them might have a typo somewhere is unworkable.
Use a version control system to track and identify changes, including accidental ones. Git is a pretty popular option - you can use it locally on all platforms that Qt's supports, or combine with one of the many SaaS services.
Good luck!
-
Hi @GuitarMan,
I have hundreds of files in this project, and having to go through all my header files to see which one of them might have a typo somewhere is unworkable.
Use a version control system to track and identify changes, including accidental ones. Git is a pretty popular option - you can use it locally on all platforms that Qt's supports, or combine with one of the many SaaS services.
Good luck!
@Paul-Colby
Thanks, Paul. I use Perforce, and it's often the only thing that saves me in these situations. But in a better world, Qt's logging would let me know the module and line number of the error.
