Could you please tell me how to debug a robot that trades on a stack of orders on Forts? Is there any tool to play the cup history or work with real data in the execution emulation mode? I can not think of anything but to debug it on a real account using print and comment, which sometimes is not cheap :(
There's one in the marketplace. The kodobase doesn't seem to have any.
There are some on the market. I don't think there are any on the kodobase.
Good afternoon, Stanislav.
I read the description of OrderBook History Library. If I understood it correctly, when connecting this library to the robot, I can replace the regular events from the tumbler with events from the emulator. When playing the strategy in the tester, the channel history broadcasting will be synchronized with the tester tick history. Accordingly, the emulation of the execution will be based on the tester tick history. If I understand it correctly,it seems that this is what I was looking for. Thanks, I'll give it a try!
I read the description of OrderBook History Library. If I understood it correctly, when I connect this library to my robot, I can replace the events from the tester with events from the emulator. When playing the strategy in the tester, the channel history broadcasting will be synchronized with the tester tick history. Accordingly, the emulation of the execution will be based on the tester tick history. If I understand it correctly,it seems that this is what I was looking for. Thanks, I'll give it a try!
You can't mention or discuss products in the forum. Questions about the product, please write to me in person.
I've discovered a strange thing with creating a graphical resource! One and the same code variant written in MQL5 works perfectly, and in MQL4 it does not work at all! Everything is absolutely the same and looks simple:
I've discovered a strange thing with creating a graphical resource! One and the same code variant written in MQL5 works perfectly, and in MQL4 it does not work at all! Everything is absolutely the same and looks simple:
Yes, it does not work in MT4. But it works for both MT5 and MT4 with this shorter design:
I thank you, but alas, this structure loads images only at compilation time and I need to load them into a compiled file at work. So the ResourceCreate() function in MQL4 does not work in any way? Maybe, the developers simply forgot to add the code for it in the busy schedule?
[in] Относительный путь к файлу, содержащему данные для ресурса. Если путь начинается с обратной косой черты "\" (пишется "\\"), то файл ищется относительно папки Если второй вариант функции вызывается для...
Thank you, but alas, such a construction only loads images at compile time, while it should be loaded into the compiled file at runtime. So the ResourceCreate() function in MQL4 does not work at all? Maybe, the developers simply forgot to add a code for it in the turmoil of events?
Allow the use of cookies to log in to the MQL5.com website.
Please enable the necessary setting in your browser, otherwise you will not be able to log in.
You are signed in. Two-factor authentication has been disabled. Set it up again and scan a new QR code, or continue with two-factor authentication disabled.
Hi all!
Could you please tell me how to debug a robot that trades on a stack of orders on Forts? Is there any tool to play the cup history or work with real data in the execution emulation mode? I can not think of anything but to debug it on a real account using print and comment, which sometimes is not cheap :(
There's one in the marketplace. The kodobase doesn't seem to have any.
There are some on the market. I don't think there are any on the kodobase.
Good afternoon, Stanislav.
I read the description of OrderBook History Library. If I understood it correctly, when connecting this library to the robot, I can replace the regular events from the tumbler with events from the emulator. When playing the strategy in the tester, the channel history broadcasting will be synchronized with the tester tick history. Accordingly, the emulation of the execution will be based on the tester tick history. If I understand it correctly,it seems that this is what I was looking for. Thanks, I'll give it a try!
Good afternoon, Stanislav.
I read the description of OrderBook History Library. If I understood it correctly, when I connect this library to my robot, I can replace the events from the tester with events from the emulator. When playing the strategy in the tester, the channel history broadcasting will be synchronized with the tester tick history. Accordingly, the emulation of the execution will be based on the tester tick history. If I understand it correctly,it seems that this is what I was looking for. Thanks, I'll give it a try!
You can't mention or discuss products in the forum. Questions about the product, please write to me in person.
I've discovered a strange thing with creating a graphical resource! One and the same code variant written in MQL5 works perfectly, and in MQL4 it does not work at all! Everything is absolutely the same and looks simple:
As a result, when you install the indicator on the chart in Metatrader 4 we have
Where is the problem?
I've discovered a strange thing with creating a graphical resource! One and the same code variant written in MQL5 works perfectly, and in MQL4 it does not work at all! Everything is absolutely the same and looks simple:
As a result, when you install the indicator on the chart in Metatrader 4 we have
Where is the problem?
Yes, it does not work in MT4.
But it works for both MT5 and MT4 with this shorter construction:
Yes, it does not work in MT4.
But it works for both MT5 and MT4 with this shorter design:
I thank you, but alas, this structure loads images only at compilation time and I need to load them into a compiled file at work. So the ResourceCreate() function in MQL4 does not work in any way? Maybe, the developers simply forgot to add the code for it in the busy schedule?
Thank you, but alas, such a construction only loads images at compile time, while it should be loaded into the compiled file at runtime. So the ResourceCreate() function in MQL4 does not work at all? Maybe, the developers simply forgot to add a code for it in the turmoil of events?
but that's the way it is:
What's the fundamental difference?
any suggestions?