Hi, I am not miro, just another bored guy, but
try setting the "A: this block can create 1 object" to "no".

Hi, I am not miro, just another bored guy, but
try setting the "A: this block can create 1 object" to "no".

I'm afraid I can't help with the separate window, I guess you need some custom indicator coding there..
I have just used the comment-block to view my formulas - the downside is that you see only the latest calculation.
Why dont you set some arbitrary stop on the order, like 9000 pips?
That's interesting strategy, power of 20...
This is one way to do it:

https://fxdreema.com/shared/6KnVT6Zke
Welcome to the forum!
Can you please make a shared link to your project? From the upper left menu.
Couple tips:
I'm not 100% I understood what you are after, but hope this will help you forward.
The logic is just for the last high close: https://fxdreema.com/shared/sQdd6Ilqb

I have made lots of similar systems, and I think this may be the most compact form:
https://fxdreema.com/shared/8HXBwss0d

Youre right.
Block amount itself is not that huge, but the mess is 
I will need to do some serious grouping and organizing if I am to keep improving this.. Its hard to remember how each block contributes - I can't imagine how the guy with a thousand blocks can keep track what is happening 
Your "y" variable doesn't change at any point.
Also, alone blocks will not work, there must always be a connection.
So you want multiple moving average crosses before trade? By default, you can only work with a one "slice" of time, be that the bar open, one tick, etc... The thing is, these multiple crosses rarely appear together on that exact moment. So you need a system to "remember" those older crosses, or alternatively, a loop that can go through multiple candles to find the older crosses. Variables will become handy anyway.
@josecortesllobat said in EA from Examples:
- connect the block #7 to the yellow output of block #3
I am not using the yellow output of a cross over condition.
@josecortesllobat Hi!
I think block #3 is a cross-block. But yeah, its best to make separate flows for buy and sell in this case.
@josecortesllobat Does the ELSE of "cross above" really mean "cross below" ?
Isn't it just "not cross above"?
Ok, the logic is fine now. Maybe its the indicator - try some simple moving average instead of custom indi, does that work?
Which candle ID are you using?
Why dont connect block 5 to block 1?
I think crossings on current candle is not very smart.
Try Candle ID 1 in all conditions, does it help?
@Moofty Oh hello
Didn't get that notification, just accidentally found this thread.
I am working with these channels too - and its a pain. I decided to abandon the "regression channel" and "standard deviation channel" objects entirely, as you cant get those upper and lower values without some serious custom code.
Instead I calculate all those lines manually, with some loops and formulas.
I can make a tutorial if youre still interested in these.
Monster keeps on growing...
I got frustrated on working with the standard regression object, so made the regression calculations manually. I should make a guided tutorial on that...
It draws decent regression channels now, next step is to utilize them better for trading. Now it just uses Stochastics cross, condition being the price is near regression line (and regression is accurate).
0_1524930347211_LINEAR3.4.mq5
13000 lines of code - my laptop processor hates me.
I am not much of a MQL coder, but I think this is going on here:

The comma after "iCustomName" means that there should be a fourth parameter to the function. Instead of the fourth parameter, the function ends with ")". That's why its saying "parameter missed".
Try removing that useless comma after iCustomName.
The warnings (yellow icon) dont mean anything really, I got 30 of them every time and my bot runs perfectly.