Do I have to use Purifier in this cumbersome way??

[kpeters58]

The Purifier window is shown in the help along with all things from the tool menu, so I assumed it would also be there....
Found it under Debugger and expected that I could perform my settings prior to running but its menu item is only enabled when prog is running???

So I set a breakpoint at the beginning of my code and then setup purifier

This seems unnecessarily cumbersome!

What am I missing?

I believe I just ran a Purifier session - I say 'believe' because there was not indication of anything after my app ended, no report, no window - nothing.
The help is mum on the topic, too, so I don't know what I should expect...

Anybody?

[netmaestro]

I use the purifier only when I'm testing quality or looking for an issue. This is because the purifier slows the execution down by factors of ten. I use it by going into the Compiler Options -> Compile/Run -> Enable Purifier and then it's attached for subsequent runs of the code until you go back in and turn it off. Also look at the command "PurifierGranularity" which you can place in your code to customize its operation depending on what you're looking for, be it string overwrites, blown buffers, mustard on your screen, what have you. The debug window will show any lines of your code where writing is taking place where it isn't authorized.

[kpeters58]

Thank you for shedding some light on the topic - the help around this needs a few sentences on usage...