Topics created by alexdepa

You can solve temporarily by declaring the variable by adding this line manually Int digits; in the mq5 file, but I am not a programmer, to solve it in the right way fxdreema must do it.

I agree with Xfire. Pleasse share tyour project.

I recommend you to contact the administrator directly via the support page.

It should be "Data producing" logic block connected to the "write to file" block. Is this what you have done?

Yep I found it...thank you!

It looks that I missed this question. Maybe there is something introduced with the new hedging mode, I need to check what is going on.

I'm aware of that right now. I'm currently trying some backup procedures on the server, but the system become overloaded and things are happening slowly. Plus, there is a 10 seconds timeout for the compiling requests, so the builder just stops waiting and nothing more happens.

First i will remove that timeout, because unfortunately even if something is fine, metaeditor.exe (which is also the compiler) always starts very slow, with at least 2 seconds delay, which makes all compilations 2+ seconds slow. Very bad, I tried to find a way to resolve this, but no success.

@valleyfx Why do I think you are asking for Break even

I still don't understand what needs to be counted. But each trade exists in the database of MT4 even after restarting the PC, so you can always loop through the history trades (or the running trades) and get different values out of them. Of course, most blocks in fxDreema are set up in a way to work with particular Magic Number and with the current Symbol (Market), so if you need to work with all available trades, then some small changes are needed in the blocks (their Filter settings).

If you cnange the parameters of the EA, I think the memory remains, but I'm not sure. If you remove the EA completely and then add it again to the chart, the memory is lost

Many thanks for your reply.

Because I don't feel good about the Martingale option as well 🙂 I told you, even I don't know what to expect from these options, as there is no other option to select from where to get information about the next lot size. I don't know, something is missing for me about these options at the moment and in general I don't like adding functionalities when I'm not sure about them at 110%. Because if I add something and it turn out to be a bad idea, in the future I will need to deal with eventual problems

MM options are not totally clear even in Buy now/Sell now. Some people wanted to calculate the next lot size out of currently running trades, which is not exactly how Martingale should work. But now this is how it works - first the running trades are checked and after that closed trades. If you know this... okay, but if you don't know about this, who knows. For some reason no one reported problems with this behaviour, but I can only imagine someone who is trying to understand what is going on sometimes.

Again, there is something that is not clear for me in these options even for Buy now/Sell now, and for pending orders things are even more complicated. Maybe I need to rething how things happen and add some more options for control, but there are like 40 input parameters currently for Buy now/Sell now and it's already ugly 🙂 I just don't like the idea of adding more parameters in blocks who already have 10s of parameters.

https://fxdreema.com/shared/qdg2pS9Wb

topic/3562

I think it's fixed already. But I always expect problems from MetaTrader 5 anyway 🙂

Yes...now it works!

Many thanks,
Alessandro

Can you give me simple project where this problem happens?

From what I see in your projects, you can have multiple trades at a time. If there is a running trade, Martingale works with the lot size of the latest running trade. Maybe because of thins it doesn't work as you expext. But what to expect when there are running trades... you know that Martingale is supposed to work with 1 trade at a time.