how can I debug script called by macro>

General Macro Scheduler discussion

Moderators: Dorian (MJT support), JRL

Post Reply
AppAust
Newbie
Posts: 6
Joined: Wed Jan 20, 2010 10:04 pm

how can I debug script called by macro>

Post by AppAust » Wed Dec 05, 2012 6:13 am

I have a script that contains dialog to get various values.
Depending on values the script then calls other scripts via the macro> command passing various paramaters.

My question is how can I debug the called macro?

Thanks.
If it doesnt need a motor, it doesnt need to be done

User avatar
Marcus Tettmar
Site Admin
Posts: 7378
Joined: Thu Sep 19, 2002 3:00 pm
Location: Dorset, UK
Contact:

Post by Marcus Tettmar » Wed Dec 05, 2012 6:25 am

You would have to open that other macro up separately, set the parameter values as variables at the top temporarily and debug.

Another way would be to use Include instead of Macro.
Marcus Tettmar
http://mjtnet.com/blog/ | http://twitter.com/marcustettmar

Did you know we are now offering affordable monthly subscriptions for Macro Scheduler Standard?

User avatar
BAM
Newbie
Posts: 4
Joined: Fri Nov 24, 2017 6:56 pm

Re: how can I debug script called by macro>

Post by BAM » Thu Dec 03, 2020 4:08 pm

Dear Marcus,
can you write an example? I have the same issue. Cannot debug a scipt calle from another scrip with parameters.
Thank you in advance.
Massimo Tivan
Banca Alpimarittime Bank
Massimo Tivan
RPA Developer

User avatar
Grovkillen
Automation Wizard
Posts: 1009
Joined: Fri Aug 10, 2012 2:38 pm
Location: Bräcke, Sweden
Contact:

Re: how can I debug script called by macro>

Post by Grovkillen » Thu Dec 03, 2020 5:45 pm

I use include for this reason, the code in the included file will be shown in the editor when you run your code.
Let>ME=%Script%

Running: 15.0.24
version history

User avatar
PepsiHog
Automation Wizard
Posts: 511
Joined: Wed Apr 08, 2009 4:19 pm
Location: Florida

Re: how can I debug script called by macro>

Post by PepsiHog » Sun Mar 14, 2021 6:01 pm

The way I prefer doing this is to combine them together. Eliminate the macro call. Then debug. Once it works, split the two apart again.

Include shows the code included when it's running but then disappears when it stops. Makes debugging difficult.

Good Luck,
PepsiHog
Windows 7

PepsiHog. Yep! I drink LOTS of Pepsi (still..in 2021) AND enjoy programming. (That's my little piece of heaven!)

The immensity of the scope of possibilities within Macro Scheduler pushes the user beyond just macros!

Post Reply
Sign up to our newsletter for free automation tips, tricks & discounts