Paul A Bristow

Thanks for working on this. I'm a Windows 10 user, so I'm not sure how to test this patch (and not using CodeBlocks just now - reverted to Visual Studio and even VS Intellisense is choking on my input ;-( ).

Well if it is tricky to fix properly, how about just removing the 'Yes' button? This means that the user HAS to shut down 'properly' - what he should have done in the first place! For a bonus, tell the user how to do it properly in the popup box (close the run window).

Hmm - sounds more trouble than I need - there are too many of my own bugs to fix! I think I'll wait untilt he next release. But thanks for tackling this buglet.

I’m not sure how to apply this patch to my setup (and worried to see that it appears to be GCC specific whereas this behaviour is found with Clang too). If you want me to test this patch, please tell a novice patcher if and how to do it. (Meanwhile I have stopped being naughty and close things down properly 😉 so I can wait for the next CodeBlocks release.) Thanks for looking into this trickier-than-it-appeared buglet.

Are you quite sure that INPUT = /home/USER/SCRATCH/OFFICIAL_CHANGE/TEST/doxytest directory contains your .h file? Try changing it to .for ? to check if your alias is working as expected?

I suspect that you need to show the details of your doxyfile? Are you sure that you have asked to process the .h file?

Thanks for confirmation :-) https://sourceforge.net/p/codeblocks/tickets/976/

"Currently compiling. Stop compilations and exit?" - replying Yes causes a hang.