I'm not aware of such possibility, OrderClose() does not have "comment" attribute

No, this block doesn't exists in the PC version

Looking at your latest project, you failed in this rule - https://fxdreema.com/demo/mt4-wrong-closing-rule Make sure you understand this first

Hi
Thanks I have tried this then figured out the the EA's where switched off in MT4, since I re-installed it.
Many thanks again for your help

__Look at the examples - https://fxdreema.com/examples/
Look at this one - https://fxdreema.com/demo/mt4-wrong-closing-rule
Also look at this one - https://fxdreema.com/demo/mt4-loop-how-it-works And then the others -[/quote:21vh79fz]

OK, thanks for the reply and I will take a look.

Oh my god
Thank you. It was my faul i wrotte it wrong. Now is correct. 😄

https://fxdreema.com/shared/IGWcDxu1c

Thank you so much
I know my mistake now and I fixed it.

I understand i will take one look on the skip the "n" part.

I hope you can change those parameters for us to control each trade and open time...

If you any news, can you update this topic?

Thanks in advance!

Now you have 2 for cycles one in another, not one after another. Is this your idea...
At this hour of the day my mind doesn't work very well, but these are for loops and if something is wrong, it's probably something logical. But also these loop blocks are not very useful, you probably need to break the loop at some point.

You know, weeks ago I added some more options for My Indicators. These options - http://prntscr.com/aglznm The problem is that they are only for custom indicators and Fractals is a built-in indicator.

The only advice I can give is to use less blocks as possible and to connect them in more optimized way, which is something full of depends. Even I don't know everything that happens in MT4/MT5. Other than that, what can you do really... It's my job to make the EAs run faster, but this is not always easy

The tester gets information from the history data, I don't know how can you change the time

You are doing things blindly. And I am even more blind, because I don't even know how your indicator looks like. But once you understand indicators, it's not hard at least to find what the problems are.

Here the first two examples are showing how to inspect values, including indicator buffers - https://fxdreema.com/examples/#Tips-and-Tricks

Before using any indicator make sure that:

the indicator can be loaded, works well and there are no error messages in the logs you know it's values

I also don't really understand what you are trying to do 🙂 Sorry, check this, check that, lot sizes... and more than 15 other questions to answer 😄 I have no ideas, I'm not thinking for strategies, I prefer to answer to very specific questions 🙂

Well, it didn't work. I had very strange results.

I'll think about something else...

There are obviously 0 blocks for converting, otherwise you will see some category called "Converting" or something.

It looks that now I must think for these things as well... Anyway, just in case, there are some native conversion functions like this one - https://www.mql5.com/en/docs/convert/stringtotime

Thanks Fxdreema, I will give your suggestion a go

Thanks. I had achieved the same result using counters. But it was way more long-winded.
Thanks for pointing that out. Will amend my EA

I have to check what is going on in these Trade Statistics, but I will recommend to NOT use them if possible. These work on a global level including all Trades/Orders. The EA itself is supposed to work with it's own trades and orders (most of the time). Because of that there is something called Magic Number. Manually created trades have Magic Number equal to 0. Otherwise it's some different number. Here is more about it - https://fxdreema.com/help/-/working%20w ... d%20groups

Everything is possible at code level, but I will not add such thing as an option

Well, it depends how you define "each time the actual price moves x pips away, from
a moving average indicator". The price is moving up and down all the time => indicator values as well (mostly for the current candle) => multiple crossovers actually happen in short periods of time. That's why I put this Turnover parameter, which is the size of the path the price must travel backwards before the block decides to give you signal for the same crossover again.

Otherwise if you only want to check whether the current price is above some level, use "Condition". It also has some type of crossover that is a little bit different that this one. Here is more about it - https://fxdreema.com/demo/mt4-crossover-indicators