terrypin Posted August 12, 2018 Report Share Posted August 12, 2018 Does anyone know why using a breakpoint on a command could change the behaviour of a macro before that command? The initial section of the macro shown here simply opens the properties of a file selected in Win 10's File Explorer. But, running it with F9, when it stops at the breakpoint, the properties window is nowhere to be seen. I eventually found it hidden under the Script Editor. And instead of two '<CONTROL><TAB> commands it had executed only one, so that the Security tab was selected. If I removed the breakpoint and instead inserted a Pause directly before the Mouse Move, I got the correct result: the Properties window was on top and its Detail tab had been selected. Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.