Posts made by fxDreema

How "Indicator rise" works...

You load the indicator. By default it is with Candle ID = 0, which means that it's current value is used.
The idea is that for X candles in the past, that indicator is rising (every next value is bigger than the previous one). So, we start from from the Xth candle in the past, then the next one (X-1)... depending on how many candles are chosen, until we reach the candle that is chosen for the indicator (Candle ID).

I just edited the behaviour of "Candles to rise" so now when it is 1, that means that the block will check if there is a rise between the previous candle and the current candle of the selected indicator.

http://fxdreema.com/shared/ucFKJ0TJc

Test that in M30, you will not see many arrows as a result... if any. That's because in the moment of a new bar's creation, the current and the previous ADX value is basically the same in M30. Test it in M1... there will be many.
Remove "Once per bar" in M30 and there will me more arrows, because now it waits all bar long for ADX[0] to rise.
The situation on the right is identical, but with Condition.

I also noticed that ADX value does not update on every tick, there is probably some treshold.

Anyway, everything depends on the timeframe, first candle, last candle and the distance between first and last candles.

" and then " and then + and then Symbol() and then + and then " and then "

That's a shame - the most basic thing is not included somewhere in Condition block. Now I can suggest this: http://fxdreema.com/shared/aEO5e954, but I will include it later (these days), because now I have some other things to do.

Group should work, but more for pending orders, because positions are already grouped by their market (symbol). So you can't logically group two positions of EURUSD, because there are no two positions at all, it's always only one position. But I think you can use Group to group two different position (EURUSD and GBPUSD for example) if it's easier to manage numbers like 1, 2 instead of EURUSD and GBPUSD...

I can admit that I don't have good experience with multicurrency strategies, so in fact I never cared about the Group number in MT5, for a single marked it always work. In the beginning I wanted to make MT5 strategies to be able to work with virtual trades, similar to how it is in MT4... and that's why I keep MT4 and MT5 blocks very similar... but this is still no fact and I think it will not be

Well, I can remove this Group parameter from MT5 if it's not really needed, but I guess someone who backtests multicurrency strategies should tell me that it's not helpful at all.

"Candlestick pattern" checks all the points (Open, High, Low, Close) in relation to the oldest candle's Open price. It can't check only this - if High[1] ~ High[2]. Additional check is needed for this: http://fxdreema.com/shared/tECRAfxBb

Aaaah, try with 2 for "Candles to rise". For some reason I made it in a way that this number describes the number of candles who participate in the calculation, and you have minimum 2 candles that you can do calculations for. I wondered if this is correct, or it's more correct to say that you can have 1 candles to rise... so I think I can edit this behaviour in the future, but I'm not really sure that I have to.

Rise mode -> Rise with certain value (Value to rise)
Fall mode -> Fall with certain value (Value to fall)

Hello,
I can see you are just registered, and I can tell you that if you want to create some EA with this tool (fxDreema), you must understand the basics. This is with everything by the way...

So, it's good to know what are these events above - on Init, on Tick, on Trade...
When using loop blocks (pink blocks), to know how to use them. By the way "(in loop) Add to volume" does not work for pending orders, because it's not only the volume that needs to be specified for orders (open price is needed).
Know how to mahage groups of trades/orders by using the Group # parameter. Here is more about it.
And also variables and constants...

And in some cases there is more than one way do to something, it depends.

This is probably not what is needed, but at least it shows something: http://fxdreema.com/shared/7gvjOLCsb

fxDreema is free to try, projects like this can be always exported, so... try it

Rise mode -> Rise with certain value
Fall mode -> Fall with certain value

Put "Once per bar" blocks below conditions.

But the body size is almost free to be any size. Better use 100 +0/-0 for the oldest candle. "Candlestick pattern" matches all points in relation to the oldest candle's Open price, this is the base point from which the position of all the other points are calculated. Basically you define a zone where you can find some point, for example High point of X'th candle, and this point is related to the oldest candle's Open price. If that zone is open (+/- values are off), then that point does not matter, it can be anywhere. I don't even know how to explain this

Everything is in the output code, find this function named "ListOfIDsConnectedToMe". This function is automatically generated and depends on the blocks structure. Every block is represented in MQL4 as a normal function, so you have network of functions at the end. "AND" block needs to know which blocks are connected to it, so it can wait for all of them to reach it in order to pass at the end. So, every time when "AND" is executed, it searches for data in "ListOfIDsConnectedToMe", but this searching is very primitive as I already said, and it's probably slow.

"AND" block is to be used when 2 or more blocks are connected to it, but those blocks belongs to different groups of blocks. Imagine that you have group of 5 blocks on the left and group of 7 block on the right, and you want to check if you reached a point somewhere in the left group, and somewhere in the right group. Obviously it will be hard to connect some blocks one after another when they belongs to different groups of blocks, but in this case "AND" can help.

In all the normal situations I recommend to just connect blocks one after another. In this way when a block pass it immediately and directly calls the next one.

"OR" is useful when you have 2 parallel conditions and there is a chance for them to be true at the same time. If you have two blocks connected in parallel, and they both are true, each one of them will pass and will execute the next block(s) twice.
But there is a way to connect blocks in order to acheive OR functionality by using the yellow outputs.

I added this option, check it out.

Your project (the one you posted in this topic) does not work properly because you check for crossover in the moment when a new candle is created, but in this moment the candle looks like a small point, it has no body and wicks, so it's not a good idea to check for crossover in this way.
The alternative is to put "Once per bar" after the conditions (two "Once per bar" blocks), or to work with Candle 1, which is already fine - with body and wicks.

I don't recommend using "AND" and "OR" blocks if not really needed. Especially "AND" block is not needed in most cases. There is a map of connections (an array in MQL code) and when these blocks are used they always search into this map to know what is happening. And that mapping system is very primitive, because MQL lacks of good array functions. Well, I can't explaing it very good, but the point is that when these blocks are used - more resources are used. And that should be no problem in demo/real working because even the slowest EA is super-fast in this situation, but it's important in backtesting. But this is how AND and OR are working today... maybe someday I will optimize them more, who knows. Currently I'm optimizing the website itself, MQL follows.

Formula blocks and variables are fine, there is no problem of using as many variables as needed. I mean, if you define 10000 variables it will be the same. But if there are calculations that sucks energy, like indicators, I can advice to connect them in a way that the one that gives rare signals is above. Also, these blocks like "No trade...", "Check trades count"... when they are more they can slow down the EA.

To be hones, there was no priority for EA's builded with fxDreema to be as fast as possible. The most important was the functionality and all the options. But I think that I will create functionality to track the speed of the blocks, at least this is something I want to see, so I hope that i will do something about it. The small problem is that it's not so easy for me to modify the currently existing blocks, compatibility issues

How a candle looks at the beginning? "Once per bar" happens when a new candle is created, how is this candle looks like at this very first moment of it's existence?

Candle = 1 candle, not more
Candlestick = 2, 3 or more candles

"Single candle template" - as it's name shows, it is to be used for a single candle
"Candlestick pattern" - useful for candlesticks - 2, 3 or more candles in a row

http://fxdreema.com/shared/mFM2obdBb
but don't expect too many matches. This checks candles with ID 1 and 2 (because Pattern Offset is 1). Make wicks with greather tolerance for more matches. Additional filters are needed to detect downtrend/uptrend situations.

You are asking for indicator, but unfortunately fxDreema is not an indicators builder and it can't do that.

I told you, it's important where "Once per bar" is placed - before or after the condition. Every "Once per bar" block has independent internal memory and it knows if it was passed for the current bar, or not.

What's wrong in your project is that when a new bar is opened, you ask if there is a crossover. Crossover (x>) in case of Candle Close is:

if CandleClose[0] > indicator AND CandleClose[1] < indicator

Normally it's like this:

if CandleClose[0] > indicator[0] AND CandleClose[1] < indicator[1]

... but your indicator is just a horizontal line.

Oh, I think I know the problem... you have Once per bar, and then you check Candle 0. But Candle 0 is just opened and it does not have a look. Maybe you want to work with Candle 1, ot to place Once per bar after conditions.