Comments on: The Essential Noisy Debug Hook for Qt http://hostilefork.com/2012/10/02/the-essential-noisy-debug-hook-for-qt/ a disgruntled developer taking a stand in the information multiverse Fri, 24 May 2013 03:01:06 +0000 http://wordpress.org/?v=2.5 By: Hostile Fork http://hostilefork.com/2012/10/02/the-essential-noisy-debug-hook-for-qt/#comment-1324 Hostile Fork Sat, 17 Nov 2012 21:56:12 +0000 http://hostilefork.com/?p=162#comment-1324 @DavidStone: Done! @DavidStone: Done!

]]> By: David Stone http://hostilefork.com/2012/10/02/the-essential-noisy-debug-hook-for-qt/#comment-1323 David Stone Fri, 16 Nov 2012 01:36:11 +0000 http://hostilefork.com/?p=162#comment-1323 A better stackoverflow post to link to about warnings is probably this one: http://stackoverflow.com/questions/5088460/flags-to-enable-thorough-and-verbose-g-warnings/9862800#9862800 Of course, I may be biased because that is my post, but I used the page you linked as a starting point. I then went through the gcc documentation, removed warnings that were implied by other warnings and added anything that was missing. I then removed a few "bad warnings" and documented why I did so. A better stackoverflow post to link to about warnings is probably this one: http://stackoverflow.com/questions/5088460/flags-to-enable-thorough-and-verbose-g-warnings/9862800#9862800

Of course, I may be biased because that is my post, but I used the page you linked as a starting point. I then went through the gcc documentation, removed warnings that were implied by other warnings and added anything that was missing. I then removed a few “bad warnings” and documented why I did so.

]]> By: Hostile Fork http://hostilefork.com/2012/10/02/the-essential-noisy-debug-hook-for-qt/#comment-1322 Hostile Fork Thu, 15 Nov 2012 04:03:03 +0000 http://hostilefork.com/?p=162#comment-1322 @kkoehne Indeed, thanks! Oddly enough I'd done this in my <a href="http://hostilefork.com/hoist/" rel="nofollow">Hoist</a> library, so I was actually using an abstraction other than <code>QMessageBox</code> which handled that case. I just forgot to mention it in the initial post! I've updated with an alternative that will abort on any non-debug-spew information in a worker thread, so you know what's going on! Seems better than sweeping it under the rug, but that's how I feel about compiler warnings too... @kkoehne Indeed, thanks! Oddly enough I’d done this in my Hoist library, so I was actually using an abstraction other than QMessageBox which handled that case. I just forgot to mention it in the initial post!

I’ve updated with an alternative that will abort on any non-debug-spew information in a worker thread, so you know what’s going on! Seems better than sweeping it under the rug, but that’s how I feel about compiler warnings too…

]]> By: kkoehne http://hostilefork.com/2012/10/02/the-essential-noisy-debug-hook-for-qt/#comment-1315 kkoehne Sun, 07 Oct 2012 12:50:02 +0000 http://hostilefork.com/?p=162#comment-1315 How about just getting the Connection error fixed upstream (Qt 5)? Anyhow, to make your code bullet proof you should probably check whether the message handler is actually called from the GUI thread before trying to pop up the message box. How about just getting the Connection error fixed upstream (Qt 5)?

Anyhow, to make your code bullet proof you should probably check whether the message handler is actually called from the GUI thread before trying to pop up the message box.

]]>