Sanks... all good.

i got it working thanks. 🙂 its for when initialising the ea starting parameters.
im currently using that 2 buffer variables method for the on ticks section.
it would be great to have this as a feature next time though .

There are conditions and conditions. In your case, both conditions are crossovers of two different indicators. But the crossover happens in one candle and then it's over. At least one of the conditions should be > or <, and I wrote about this above.

If you think that after the first condition becomes true, the second one waits to become true... this is wrong. Here is why: https://fxdreema.com/demo/mt4-wrong-closing-rule
Blocks 60 and 61 are executed on every tick, again and again. While you don't have any trade, blocks 55 and 57 are also executed on every tick. If the condition in block 55 is true, only then 62 will be executed (in the very next moment, not within seconds or minutes or hours). If the condition in block 57 is true, only then 63 will be executed.

Hardly possible. But Why? 😮

It is possible to draw objects on subwindows, but for things to be simple I didn't used this option in the blocks. Maybe there is a better way of doing whatever you want to do? What if you draw another object, like an arrow?

For each Trade is the important block here. You can run this block once, and it's orange output will be active 10 times in a row if you have 10 trades. Of course, this is not mandatory, because the block has filter settings, so you can choose to skip some of the trades. And in your case the block runs on every tick.

Then you have once per trade/order - this one monitors trades/orders that For each Trade is loading and it will pass once for every unique ticket number. It has something like private database where it writes ticket numbers that were passed once. Note that this private database is deleted when you reload the EA 🙂

So, even if block 2 passes 10 times per tick, on every tick, the check profit block is reached only few times. As many times as many trades are created. For example, 10 times for the whole lifetime of that EA

you can do it this way too 🙂
theres quite a number of ways to do it with fxdreema

......
MACD.xml

I understood something about the problem...

The trailing stop starts from the open price and not the opposite bid/ask...

One example: in a BUY OPERATION the buying price is ASK but the Sell price is BID when the trailing stop starts it considers only the ASK price !

Is there a way to use the opposite referral price ?

In a BUY operation the referral price for trailing is BID
In a Sell operation the referral price for trailing is ASK

Maurizio.

Damn, this indicator has some big code 😕 But if you want to get values from this rectangle, you can do it 🙂

That works!
thanks!!!! 😄 😄 😄

It always happen to me to do something stupid as well, we are on the same boat 🙂

Use "Indicator tester" block to test and find buffers, like this: https://fxdreema.com/demo/mt4-indicator-tester
There is more info about indicators here: https://fxdreema.com/documentation/gett ... indicators and here: https://fxdreema.com/documentation/proj ... indicators

"Indicator appear" works when indicator value goes from EMPTY_VALUE (or 0) to a price level

https://fxdreema.com/shared/vdsS1O2Ec

Something like this, but not this. The problem here is that new pending orders are created every day, and at that time there can be an old trade still running. Then, because I used "No trade/order exists", a new pending order is created when everything is closed (no orders, no trades) and at these moments the last closed trade is... who knows how old is it. Some trades will be missed.

https://fxdreema.com/shared/0FhOX0hN

This is similar, but not the same. Note that "once per trade" have memory that is cleared when the EA is reloaded.

At least you can get some idea 🙂

Here is some way to do that: https://fxdreema.com/shared/bA2I4HVQ
The other way is to calculate SL and TP before Buy now/Sell now
And the other way is if I add "% of..." options in Buy now/Sell now blocks, similar to block modify stops. In any case, what do you prefer - % of... (where you write values like 100, 200, 50, 25) or times from (where you write values like 1, 2, 0.5, 0.25)?

Hopefully, but the chance is that this parameter does not work at all, because the broker itself does not work with it 🙂 I think I read somewhere that this is normal for ECN brokers.
Someone was asking the same question and I did some tests with OrderSend() and different values for it's slippage parameter - I still got trades with slippage, no matter what value for slippage I used, and I tried values like 0, 1, 10, 100, 1000 and negative values. I don't remember which broker I used for this.
Don't rely on this parameter too much 🙂

Thank you very much 🙂

I appreciate your help, I was going crazy to do this 8-)

I use it for trades in sequence, it is convenient for me to see on the chart in which sequence the EA is currently (sequence4, sequence5 etc.)

If I quickly want to change something in the EA when a sequence occurs I just pop the check "status" block in there. Easy, simple.

Put the output .mq4/mq5 file here (project data is appended at the end of the file). Also .xml file can be exported

Nevermind I figured it out. I actually had to use 2 for the candle ID.

Thank you, you are really great.

This tool that you made is amazing.