Comments welcome, hope you find it useful if you didnt know about this.
well done… flow it into claude code and claude desktop and generate template code to implement it in embed points? certainly a great example.
No need, I think Capesoft have a template called BreakIn.
My template would create a hotkey on every (window) procedure, which in turn calls an Assert(), and thus break in to the app using the debugger and processid.
My example just calls the debugger using the PID, so I expect @Bruce or @Vitesse will incorporate the cladb -p into BreakIn.
Well I’m pretty sure Geoff Robinson won’t be doing it 
- I think maybe you’re thinking of Geoff Thomson, which is someone quite different.
I’m also not really sure what incorporating cladb into BreakIn would do. BreakIn is for observing where in the code each thread is, and I’m not sure jumping over to the debugger would do any good.
I thought @vitesse did work for you. Not to worry.
Anyway, I’ve just added another example: Example7AppGenAssert.
Shows how to use an Alert key (CtrlD) in an AppGen procedure to trigger an Assert and in turn call the Debugger to step into it. Now this could be templatised easily.
Screenshots of the template which provides reasonable flexibility for ABC and CW20 (Clarion) template family. (any other template families?)
Global template, cascades settings to every Browse, Form, Process (non source code) procedure template.
Each Procedure template can be individually disabled or reconfigured.
Cant think of anything else to add to the template at this stage, but if anyone has suggestions, let me know and I’ll probably include it.
General Tab
Debugger Properties Tab
Debugger Procedure Call Code
A C6 version will follow as it involves rescaling/repositioning template controls for the reduced width.