The mistake is that it does what a custom indicator should do, but EAs are not really the right place to do Indicator's job. You can see in the code how much stuff is in there and how complicated it looks - it's because of that. And I also think the performance is lower in this way. These blocks was some of my ideas that I wanted to try, and because I am not an indicator guy... this is the result 🙂

another (similar) practical application of this feature that would be really useful - if there was a "New new top in trend" or "New bottom in trend" in the previous bar (or previous n bars), then execute orange output.

Преименувах индикатора и всичко е наред....

Благодаря

Sorry. Didn't mean to confuse you. Anyway, all my sentiments were well meant! 🙂

Maybe this option is not very good, or the way the block reacts to it. These blocks are pretty old now, I have idea to get rid of them and move their functionality into "Buy now" and "Sell now" blocks as MM options... but when, if, how... I don't know 🙂

I think the "Once"-off blocks are good to keep or at least as the default number of passes because people will mostly use them. But occasionally you need the multiple option so, in my opinion, you could either:

A)
Create the "N times per" blocks and put them in the list under the "Once" options as they appear like this:
Once per bar
N times per bar
Once per day
N times per day
etc.

B) add the "N times per" functionality to the existing "Once" blocks and revise the titles like this:
Once (or N times) per bar
Once (or N times) per day
etc.

Once/N times per bar
Once/N times per day
etc.

I would probably go for option B) with the second naming convention "Once/N times" and set the number to 1 as default 🙂

After the backtest everything you see is from the last moment of the candle. And when you values to detect signals from the current candle, they are temporary, especially in the beginning of the candle (when Once per bar is on the top). When Once per bar is below the conditions, then you work with the middle of the current candle. To work with finished candles, set Candle ID to 1 everywhere. In this situation I got this: http://prntscr.com/2loqu5

gReferansHigh_1 is some variable that is used from this EA to hold value. How this variable is used outside these conditions... I can't tell. But you can search for it in the code and you will see where it is defined (this will be like "double gReferansHigh_1...") and where it is used.

There are at least 2 ways.

One way is under "on Tick" - something like: No trade is running -> Check last closed trade profit -> Delete pending orders The other way is under "on Trade": (on trade) Trade closed -> Condition (where you will check the profit, use (on trade) category) -> Delete pending orders

I think I prrefer the first way, because in MT4 for "on Trade" to work extra resource is needed, but only if you have some blocks there 🙂

iCustom allows many input parameters without giving error message.
This gives this error:

iCustom(1,2,3,4);

This does not:

iCustom(1,2,3,4,5); iCustom(1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17);

so if it have more than 4 parameters - everything is ok with this function, it does not actually read if something in the indicator is right or wrong.
http://docs.mql4.com/indicators/icustom
This function IndicatorMoreShift() should work without parameters. So from that screenshot for me everything looks fine, or at least I can't recreate this here.
Is it possible that another function is responsible for this error?

Dynamic value works a treat, thanks for the advice.

Cheers

It is difficult to choose between MT4 and MT5. I'll try the new MT4.
My way is :
1 Calculating the price changes that have occurred in recent years
2 What dynamic calculations variables can be calculated , which automatically adapt to the current and future changes?
3 Use of FXDreema
4 To obtain Optimization Basics
5 Invigorate the basic data for all eventualities
6 Programming in FXDreama
7 validate in Metatrader tester
8 Demo test
9 validate
10 live
11. hope to win

Item: Calculation of % of Balance for an account (1 Standslot: 100.000 pcs):
Lotsize = (%ofBalance/100)*Balance/Lotsize
= (100/100)*2000/100000
= 0,02 Lot

Fxdreama calculate 0.03: see attached ea

......
Prozent of Balance.mq4

Ok i make it this
http://fxdreema.com/shared/weYx1sOKc

Now start when new day will come

http://fxdreema.com/demo/mt4-wrong-closing-rule

As I said above, any block that is on top of other blocks (nothing is connected above, at least one block is connected below) under "on Tick" will be executed on every tick. In other words, you can have multiple groups of blocks ane they all will be executed in the same tick one after another. What will be in these groups of blocks... your choise. It can be Condition -> Buy new trade, it can be Condition -> Close trades.

yes, that's the one - didn't recognize it. thanks 🙂

What formula? Formula block does simple calculation and saves the result in a global variable (result), which can then be used in other blocks. But I can suggest to work with Variables.

Ooops, wrong address 😳
http://fxdreema.com/shared/DkTazQIQc

Yes, but if you don't want to do it once per bar you can always remove that block, and you will remain with No position -> Condition -> Buy now.
If you want to be able to create new position within the same bar, I can suggest to set that block (Once per bar) to work on lower timeframe.

When dealing with pink blocks, especially for MT4, it's better to always use "For each Trade" somewhere above. Read the description of "For each Trade" for more details.
Also, I think "Once per trade/order" should be placed after that condition. You have the same situation type as here: topic/2313