Topics created by isp00rt

I'll try to filter it. If I don't get it I will let you know. Thank you for your help.

I've done something like this before...

I used the ticket number to select a specific trade.

Maybe some picture? I don't really understand what "both Stop levels" mean, because it could mean SL and TP of the same trade... because SL is a stop, but TP also stops the trade 🙂

Thank you very much for your explanation. Now I understand it much better. I will try what you suggest.

Hello

I have found a way in one of the @miro1360 post

https://fxdreema.com/forum/topic/4608/field-comment-to-sell-now-block/2

Thanks

Ok. Thanks.

I found the origin of those weird numbers. They are the SL of another trade!!! 😮

Look at this:

0_1532614904144_01.png

The bottom trade was the first one to be opened with that stop level. As you can see its SL level was 'caught' I don't know why and then used in other two charts. However the EA worked well in all other charts. This is certainly a bug. I will copy this message at that subforum too.

Ok. Thank you.

Ok. Thanks.

Many interesting ideas to explore. Thank you all for them. I'll try them ;).

I'll try. Thanks.

Apparently it was a kind of random error. I've been testing for a week now and apparently it works smoothly. Weird.

In this block you load a custom indicator and you choose one buffer. I don't care what the indicator is and what is the number of the buffer, this block does the same. It expects the values of the buffer to be EMPTY_VALUE or 0 most of the time, and only from time to time to be something different, lets's say the price value.

The idea is that every buffer has as many values as many candles there are on the chart. If each value is a positive number that can be seen on the chart, then you see something like MA line. But some indicators don't want to draw continuous line, so they use that EMPTY_VALUE value, which is a MQL constant that represents the biggest possible integer value.

"Indicator appear" checks the indicator every time it runs and remembers its last checked values. If the last checked value was EMPTY_VALUE and the current value is say 1.2345, it passes.

I also set it to work with value 0, because some indicators use 0 instead of EMPTY_VALUE.

Ok. Thank you.

Well, I saw a different name for that block. This is why I thought it was a different one. Once again, thank you very much for your help.

Sorry I was wrong, but maybe this can help you

https://fxdreema.com/shared/BTkwL64Sd

Ok. Thank you.

Interesting. I'll try it.
Thank you.

Here I am again after some testing has been done. Certainly it works better now, but no completely fine. Let me show you my results.

Test conditions:

Automatic trades instead of manual ones. I used a different EA opening trades an then, on a separate chart, the pipcounter EA. Obviously the same magic number was used on all of them.

A total of 5 charts were used simultaneously, all of them having different point rules.

No previous closed trades were available for the test. That means the number of pips for closed trades at the beginning was exactly 0.

And this was the outcome. After a few hours, three trades were closed, with the following results:

0_1515582302991_001.png

These are the numbers. The USDJPY trade was closed with a positive 5.5 pips. The first JP225 trade was closed with a negative 10 pips an the second one with a negative 26 pips. That means the overall resul for closed pips should be 5.5 - 10 - 34 = -38.5 pips.

Sadly, this is what I got:

0_1515582608140_002.png

This is a screenshot including a fourth open trade correctly counted, as you can see. The problem is, once again, the count of closed pips. At first glance, the number shown (506) seemps completely random, but then I tried to figure out why it was so. This is my bes guess of how it was counted:

550 pips for the positive USDJPY trade minus 10 pips for the first JP225 and minus 34 for the second equals exactly 506.

That means that both JP225 trades were correctly counted once closed, but that was not the case with the USDJPY that was multiplied by 100. Then I took a look at the point rules for three digit charts and I confirmed that they were 0.001 = 0.01. And this is not the correct result.

Any idea why the EA is only partially counting pips correctly?