AutoHotkey Community

Hey, just got a great idea, since BigVent gave tips to new ppl.

He mentioned that one could put Msgbox all over the code to tell what's happening, and i recommended outputdebug as it isn't super duper important that you remove it afterwards. and it's also simple to remove later as you could use Search and Replace functions that a lot of text editors has, to comment out the outputdebug lines...

So i thought why not go further:





Basically, before the script executes, it will decide whether or not it should include those outputdebug lines

Also, optionally you could add a DbgMsgbox
for ppl who prefer that box popping up...
;sry couldn't bother with writing a 'proper' post, very sorry if I'm doing it wrong...

_________________

If you don't have a program running, listening for debug messages, OutputDebug won't do anything. Furthermore, it is easy to write a wrapper function which calls OutputDebug/MsgBox if a global flag is set, and does nothing otherwise. There is no need for a "#Debug" directive.

Yeah, that may be true... Maybe, some day, I will write a script to do the search and replace stuff <_<... Kinda wanted all this to be processed before the script launches, so that there isn't any 'unnecessary slowdown'...

_________________

I had the same idea a many moons back. That's why I put in a request for a new NOP (No operation) command. No one was interested. My idea, similar to yours, was to do a mass replace of the outputdebug command with NOP before moving the script to production. Leaving the NOP commands in the script makes it very easy to reverse the search/replace and it keeps the script line numbers intact for debugging.

Oh well. C'est la vie.

OP:
NOP:
:?:
It is negligible.