Logfile with loop nr info
Forum rules
Before asking a question or reporting an issue:
1. Please review the list of FAQ's.
2. Use the search box (at the top of each forum page) to see if a similar problem or question has already been addressed.
3. Try searching the iMacros Wiki - it contains the complete iMacros reference as well as plenty of samples and tutorials.
4. We can respond much faster to your posts if you include the following information: CLICK HERE FOR IMPORTANT INFORMATION TO INCLUDE IN YOUR POST
Before asking a question or reporting an issue:
1. Please review the list of FAQ's.
2. Use the search box (at the top of each forum page) to see if a similar problem or question has already been addressed.
3. Try searching the iMacros Wiki - it contains the complete iMacros reference as well as plenty of samples and tutorials.
4. We can respond much faster to your posts if you include the following information: CLICK HERE FOR IMPORTANT INFORMATION TO INCLUDE IN YOUR POST
-
bugmenot666
- Posts: 39
- Joined: Wed Apr 08, 2009 2:01 pm
Logfile with loop nr info
It is very annoying when Imacros crashes, and one has to find out exactly when it happened. One could of course start with a fresh logfile every time, and that way decipher when the crash happened. But is there some easier way ? Could one for example have the loop number written to the logfile somehow ?
-
Tom, Tech Support
- Posts: 3636
- Joined: Mon May 31, 2010 4:59 pm
Re: Logfile with loop nr info
Hello bugmenot666,
Although this isn't currently implemented, you could easily save the current loop value to a separate file at the start of your macro.
For example:
Although this isn't currently implemented, you could easily save the current loop value to a separate file at the start of your macro.
For example:
Code: Select all
SET !EXTRACT {{!LOOP}}
SAVEAS TYPE=EXTRACT FOLDER=* FILE=LoopLog.csv
SET !EXTRACT NULL
Regards,
Tom, iMacros Support
Tom, iMacros Support
-
bugmenot666
- Posts: 39
- Joined: Wed Apr 08, 2009 2:01 pm
Re: Logfile with loop nr info
Thanks Tom. I figured something like that was the best way, but did not know that {{!LOOP}} was an extractable value. Just concerned that it might lead to more crashes and slower loop execution, but I figure it is worth it.
Have a great day. Thanks for a great application.
Have a great day. Thanks for a great application.