Strategy tester journal
What if you use the debugger to go through you code step ba step:
If the code can be compiled without any error but it doesn't do what you expect use the debugger to find out why - it is exactly made for this.
Code debugging: https://www.metatrader5.com/en/metaeditor/help/development/debug
Error Handling and Logging in MQL5: https://www.mql5.com/en/articles/2041
Tracing, Debugging and Structural Analysis of Source Code, scroll down to: "Launching and Debuggin": https://www.mql5.com/en/articles/272
- www.metatrader5.com
What if you use the debugger to go through you code step ba step:
If the code can be compiled without any error but it doesn't do what you expect use the debugger to find out why - it is exactly made for this.
Code debugging: https://www.metatrader5.com/en/metaeditor/help/development/debug
Error Handling and Logging in MQL5: https://www.mql5.com/en/articles/2041
Tracing, Debugging and Structural Analysis of Source Code, scroll down to: "Launching and Debuggin": https://www.mql5.com/en/articles/272
Thanks for the links - I'm using the debugger but haven't solved the issue yet. I wanted to be able to see my debug Print's without the terminal output, but if that's not possible, I'll have to live with it.
Hi
You can also create your own file in the EA – as a separate log file.
Simply save Print messages from the EA to the created new txt file – then only those messages would be saved in this file.
It won’t be visible only in journal, but you can simply open the file later, so after the test you can open this file and see only those messages printed from your EA.
Best Regards
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
You agree to website policy and terms of use
Hi,
I'm using the Strategy Tester to debug an MQL5 EA strategy that inadvertently issues many PositionModify commands - the journal gets full of server messages and its hard to see the wood from the trees. When using the Strategy Tester, is it possible to (temporarily) block server messages - I just want to be able to see my own debug. Also, the journal files are massive.
Thanks