Posts made by roar

yeah, "once per bar" definitely is slower than every tick action.
But in my opinion, every ea that needs to work faster than once per bar is 100% bullshit

it shouldn't lag 2 candles with this setup

Yes, if you use "once per bar", you should use id1, because id0 would always have only candle-open data.

indicators are just calculations based on some candles. you see, everything starts from the price.
so you can think candle id is actually same as indicator id

my example would surely work for the buy part.
unless you test "once per bar", then you have to use older IDs - replace id1 with id2, and id0 with id1

yes, you want the bear candle to be id1, and bull candle id0

https://fxdreema.com/shared/Kd93k3tR

I think the desktop version is not updated anymore.
But there's a simple way to work around the problem, just use some temporary variable.
Like this:

thats right

put a condition block before buy/sell block

condition: stoch > 20 to sell
condition: stoch < 80 to buy

it is up to you which line you choose, main line or signal

Fractal value is candle high or low.
A fractal formation needs 2 candles to confirm, so you will never know if candle (id 1) has a fractal or not. Use id 2

@miro1360
Oh, youre right

Two conditions:
candle close > high candle id 3
OR
candle close < low candle id 3

IDs are not negative, btw

Yes you do. At the latest candle you can now see where MA was 15 candles ago.
So, condition: candle (id 0) > ma shift 15 (id 0)
you get the same result with this condition: candle (id0) > ma (id 15)

@ggrobot said in PAST MOVING AVERAGE DEFINITION:

look at the example, , the green MA20 is shifted -15

Remove the - (minus) symbol +15

Also, you can use the ID method with indicators too, just like candles.

when editing the condition block, hit "more settings" and there you can adjust the ID.

But working with shift is literally the same as working with candle id:
MA shifted 2 = MA (id2)

How is shifting the ma wrong?

Do you mean you want to compare candle (id5) to MA (id5) ?

I think you have to use two condition blocks. First one checks simple "<" or ">" and the last one checks the crossover.
Now you can use the first condition's yellow output

How do you determine the TP in first place?

If you connect your trailing stop block to condition block's yellow output, trailing works only when condition is false