jrgreenman Posted July 27, 2010 Report Share Posted July 27, 2010 If I set break points in two macros and, during execution, the first (where I start the debugger) calls the second one, and then press F9 in the first one, execution does not stop at break points in the second macro. I'm on ver 4.1.6.1. Anyone else see this behavior? Quote Link to comment Share on other sites More sharing options...
paul Posted July 28, 2010 Report Share Posted July 28, 2010 When you invoke the 2nd macro (via a Macro Run command), you are not running the version of your 2nd macro open in the script editor. My technique for resolving this is to include the code of the 2nd macro in the 1st macro while testing. Quote Link to comment Share on other sites More sharing options...
Cory Posted August 2, 2010 Report Share Posted August 2, 2010 F9 steps over called macros the same way F8 does. This is by design. Refer to the help file Editor Menu - Debug page Step Options section for an explanation of step options. IE F7 step into versus F8 step over. I don't know of any way to change this but there is a workaround. Break the command prior to and optionally after the Macro Run. F9 up to the first point then F7 thru the called macro. Or put a break in the first command of the called macro and F9 once you have stepped into it with F7. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.