Well, MT5 works with positions and you can count them if you work with many markets. Some things in MT5 are logically different.

I can see you start counting when the EA is started... or at least it looks like this. Actually you can count over the past trades and orders using "For each...." blocks. Well, now I realized that I should add option in "For each Closed Trade" to not go to very old history trades, but at least you can specify exact amount of past closed history trades to work with.

I can suggest to define and use a variable (click Variables) instead of Formula's result variable.

Here is a little example of how to calculate lot sizes of buys and sells: http://fxdreema.com/shared/bvrTBQFKb
Or even better with this one: http://fxdreema.com/shared/NwqfdGorc
this example is better because you loop trades once, and for each of them you ask for some of it's properties (in the case - it's type) before incrementing other parameter. So you can actually loop all available trades from all groups, and within the loop to check it's group number.... I think you will get it 🙂

Read the information of these pink blocks to understand how they work. You will probably realize how this second properties panel works.
I used "OrderLots()" which is a native MQL4 function that returns the lot size of the currently loaded trade, but you can also use "Formula" or "Condition (+Adjust field)" or "Modify Variables" to modify a variable. In these blocks the given parameter (for example lot size) is hidden somewhere in the pink "(in loop)...." category.

Ah! OK. Thank you. It mostly seems to work OK. In this instance I can probably ignore this error message then, as the next iteration works, and there is always a stop in place.

Thanks again.

🙂

thanks for all it working perfect but at this moment I don't know how but I will find out 😄

OK. Will do. Thank you! 🙂

With blocks - Condition and Formula blocks. Or Conditions and Variables. This can be also written as source code if you create custom block. Something like this...

calculations, calculations, calculations... if (certain condition) {~next~} else {~inext~}

Here ~next~ and ~inext~ keywords are filled with data in the project, depending on what blocks are to be executed next (inext is for the yellow output).

This indicator has 4 buffers, but they can't be detected for some reason... I have to check that later. But anyway, you can manually fill the data for 4 buffers - click on "new..." and write whatever you want to the input fields.
http://prntscr.com/25u3k0

Break even block loops trades inside, so normally it's not meant to be used inside loop (under "For each Trade"). Read the description of "For each Trade" to understand about loops.

Break even block, when executed, modifies SL of all (filtered) trades that are in profit in this moment. So I guess you can just place this block under the condition where you check the profit. If you mean the total account profit (equity-balance).

http://fxdreema.com/examples

Mmmmm... who knows what other people are using. But you should know how fxDreema works - basically "on Tick" causes blocks to be executed on every tick, and on every tick you check some conditions and you use some filters (which are also conditions) - and at the end you have trading blocks. So if you want to buy/sell on 2 different types of signals - no problem, just add some Condition and/or other blocks in order to filter out the signals needed.

If you ask me how to buy on signal and then buy on other signal that the same indicator does not detect, well... the same indicator can't be used. All indicators are just numeric values for the EA.

None of these require server calls (if there is something about MT that I am not aware of), they interact with MT only, and MT interacts with the server when needed - and this is when trade/order is created, modified, closed. Checking trades happens locally and it's actually fery fast, so I guess the EA reads temporary variables that MT updates when new event happens.

I think i have got it thank you

Try using "once per trade/order" just before the block that modifies SL.

Pink blocks are to be used with "For each ...." blocks. Read the description of "For each Pending Order" for details.

Ah! OK. I was looking at the long "-----" line, not the "-" one! 🙂

I found that this only appears in the local version, I will fix it for the next build.

I have to say that I don't understand indicators very well and because of that fxDreema can't create or modify indicators. But if you want to create or modify some indicator you can ask in forexfactory, mql4.com, mql5.com or other forums or websites where there are people willing to do that 🙂

__Something like this, I hope: http://fxdreema.com/shared/c4T7fw43d
This can be made using "on Trade" event as well, but this should work.
The Pass once block is because in backtester there is no last closed trade in the beginning.
"Check last closed trade profit" is ugly inside, sorry for that, I have to beautify it one day.
This is probably not very well done as I created it fast, but it shows some basics and I normally prefer to show how things work instead of creating full EAs. 1 Constant and 1 Variable are used.[/quote:352vftkm]

Thank you very much. This works and i learned alot.

BR
Dark

When checked, a Variable is actually a Constant - it appears in Inputs list of the EA. But I don't recommend to check these. They exists only because one day I decided to merge Constants and Variables, but this was not a good idea.

Again it is hard for me to understand the questions. I hope this helps: http://fxdreema.com/shared/tq6Oyezxc
To put SL at the last low... it should be above Ask price.