Topics created by Xander

i Think i find a way, just where you want to draw the arrows like for example in GBPUSD, just activate the EA in GBPUSD for deploy the arrows, but make the patron recognition using the symbol filter in the other pair.

It is clearly?

Yeah same was have tried looping it with candle IDs etc and can't get it to work

Did you ever find an answer to this as I am having the same problem?

@xander this seems to work
https://fxdreema.com/shared/PchvP81Lc

@xander Correct. And the default value should be 00:00 instead of just 0.

@xander That means your broker is maybe calling that symbol in a different way. Before using that condition block just try to use your configuration in teh uimage you uploaded to stor that info into a variable. The visualize the variable through a 'Comment' block to check it out.

I email to admin hope he will have a look

@xander In that case I'm agraid I cannot offer any additional suggestion. I simply don't undertand this project. Honestly I have no idea how the 'run block' block works so maybe that is my problem. I gess you are looking for a loop to find those hughs and lows. I strongly recommend you ask for roar's help. He's ours loops expert! 🙂

I had a similar problem, to me it was because I used values of candle close for some calculations, where if you just add the indicator to the chart it will already have those close values, where if they are run live, it will calculate on every tick meaning candle close will at some point in time be every value it ever was during that tick. meaning it cna trigger a condition for 5 seconds because it reached a high value and then drop. meaning it wouldn't be true if calculated on history data, but it was true at some point during candle life.

to fix this just use previous bar for calculation. so the value cannot be changed

int -> integers like 0, 1, 2, 3, ...
double -> floating-point numbers like 0.01, 0.02, 0.03

Change "Constant Type" to double and check it out.

0_1555169879022_2226a5be-3b56-45a4-b66c-6df09c4b1c9b-image.png

After modifying the stop loss of the second trade, calculate the distance between the new stop loss and the entry price. If that distance is less than or equal to -10 pips (i.e., SL is more than 10 pips away in loss), close the second trade.

You can use "For Each Trade" block with Skip every "n" trade = 1 — this will select the second trade.

Then, use "Pips away from Stop Loss" or "Pips away from Open Price" to calculate how far the stop loss is from the entry.
If the pips from SL > first target (e.g., 10 pips), use a "Close Trade" block to close the second trade automatically.

The easiest way is to define a variable that increases by 1 when a new candle opens if there is a trade running.

int BarCounter = 0

Once per bar - If trade -> BarCounter = BarCounter+1

You have to reset that variable when there is no trade. My suggestion is to reset it when a new trade opens.

This is just an example

0_1553928120909_09a7492d-b945-40c4-b90b-59fa66c20cb5-image.png

0_1553928394714_092a7b9b-da16-444e-a438-72d2e1566460-image.png

I decided to test this block and I think it works. Here is my test EA: https://fxdreema.com/shared/AN7K8OQhd
I selected 3 different timeframes - M1, M15 and H4, and for each of them I print some information. This Delay block is to pause the EA for a while so I can see what is printer. But it looks that I need to move the chart left-right to refresh the Comment data. I see different numbers for each timeframe.

Six years later this is very helpful fpr me. Thank you very much @roar !

Well, objects are global, I don't think that the timeframe matters for them. Maybe objects can be filtered by timeframe as well, I never tried that. You want that, to access objects on certain timeframe?

This function? https://www.mql5.com/en/docs/math/mathsqrt

Thank you for the response and sorry I forgot to update this one, the project name had ":" in its name, which is fine for dreema but for some reason does not allow the EA to be created as soon as I copied the project and changed the name everything was working

Do you reset Candle ID to 0 before the loop starts?

Nevermind, found an older post with a solution by Miro, linking it here just for my reference and if anybody else has a similiar problem https://fxdreema.com/forum/topic/6372/move-confirmed-with-breakout-above-moving-average-of-volume/3