hello, I wrote a macro to create journal entries in evernote. Not only does the macro crash (‘macro cancelled’), is also reaps havoc, calling up pages, numbers and Ptouch (labels). Is there any way to debug the macro, just to see what happens line by line, ie action by action? thanks very much

[image] ronald: Is there any way to debug the macro, just to see what happens line by line, ie action by action? Yes. Before you trigger your macro, goto the KM Status menu, and select "Start Debugging": [image] This will show a popup window like this: [image] Make sure the "Pause New Ma…

Or write log messages, using something like this: [image] MACROs: "Write To Log File", etc., **Updated 2016-12-28 Macro Library MACROs: "Write To Log File", etc. UPDATED 2016-12-28: Version1.1. now includes two "ET" versions, which write elapsed time to the log. Also inc…

thank you for your excellent explanation. Works perfectly using the debugging window step by step as per your instructions. A disaster when I run it in normal mode. I have absolutely no clue why Pages, Numbers, Ptouch labels are activated, and image (?) is pasted. How would you troubleshoot? tha…

[image] ronald: How would you troubleshoot? Hey Ronald, Post the macro, so we can look at it. :sunglasses: -Chris

Here is the macro. thanks very much Chris for your time and help EN Evernote Log Diary Entry.kmmacros (27.7 KB)

[image] ronald: Here is the macro Hey Ronald, Disable all of the actions in the macro editor. Do this by selecting all of them and using the Keyboard Maestro Editor's View > Toggle Enable menu command. Reenable these one-by-one and run the macro. That way you can see the point where thing…

Hi, your method is great, and worked perfectly. It is interesting that I could not make sense of the fact that my whole computer went bananas when I ran the macro: multiple apps were activated, random pastes, etc Thanks to your suggestion: I found the solution. I had not deactivated the macro grou…

I had a complex macro running on a program repeatedly where the program was opening and analyzing an individual data file. Depending on the data, the program would pop up unexpected dialog boxes, which wreaked havoc with my macro. This might occur every 30 or 40 datasets, so the macro would run fin…

WOW !! very smart. I solved my problem but will keep this in mind. Thank you very much !

How to debug a macro?

order:views order:latest order:likes

status:open status:closed status:archived status:noreplies status:single_user

category:foo tag:foo user:foo group:foo badge:foo

in:likes in:posted in:watching in:tracking in:private in:bookmarks in:first in:pinned in:unpinned

posts_count:num before:days_or_date after:days_or_date

How to debug a macro?

Options