Posts made by fxDreema

I will fix it, thank you

Then this is not easily possible in the EA builder, because you need to check the last X candles for crossover. Loop like this does not exists now in the EA builder. It can be written as a custom code, and maybe the lowest timeframe should be used.

But note that there can be difference if you get Ask/Bid before of after Buy/Sell blocks. You know... it takes time to send the trade request.

ooops...

The current Bid price is easy, the first option in Market Properties (in Condition)

Why is that horizontal line needed?
If you just want to open new trade near the crossing of two trendlines, something like this might help: http://prntscr.com/5f8itb

Try the block named "Indicator appear", but first find which indicator buffers are responsible for these "colors". Here is more for indicators: https://fxdreema.com/documentation/gett ... indicators and https://fxdreema.com/documentation/proj ... indicators

I think so. I don't remember if I checked this one, but you can always do it with two "Print" blocks

Haha yes, the next number is the greatest + 1

Here is a little trick that works for now. You can use ID that is not numeric, for example "z", "a" or even "last", and it should be executed last.

It will not come very soon. I don't know really, this is just an idea. I just want to get rid ob block IDs. Sometimes when I want to find some and there are tens of blocks, it's hard. The "Run" block will have some alternative, because I also have plans to make possible to create pages with blocks within the same event workspace.

You want to be sure that some block will run last, after each other blocks in the same event? If this is the case, ID numbers matters here. But as you probably know, I have idea to make positions of blocks to be important, not their IDs, so in this case the block that is on right will run after the one that in on left. For now... IDs.

Profits are what you can see for each trade in your MetaTrader. Here is what I got: http://prntscr.com/5f03vj using this: https://fxdreema.com/shared/iVoOTruTc

If you have 3 trades for example, when you run "For each Trade", it does this:

1. It loads trade 1 and runs the blocks below the orange output. In these blocks you can get information from trade 1 and you can modify/close only trade 1.
2. It loads trade 2 and runs the blocks below the orange output. In these blocks you can get information from trade 2 and you can modify/close only trade 2.
3. It loads trade 3 and runs the blocks below the orange output. In these blocks you can get information from trade 3 and you can modify/close only trade 3.
4. It now goes to the yellow output. Trade 3 remains loaded, so if you put "close" here, you will close trade 3.
   ...
5. On the next tick, or when you run the same block again, it will do the same.

Of course there are filter settings inside, so you can for example skip trades 2 and 3 and not going to the orange output for them.

Haha, this problem was really old and this is the first time I get report for it

fixed

These variables should not appear, but they does not break the strategy anyway

I still believe that you don't know why "For each..." blocks exists. These are not because I want to torture people with must-have blocks. "For each Trade" does many things actually, one of which is that it loads trade "X" at a given moment. When trade "X" is loaded, you can get it's profit, not the profit of trade "Y". When you load "X", you work with "X", not with "Y". The other function of "For each Trade" is that it repeats itself multiple times - as many times as many trades there are to be loaded. So if now you have "X" loaded, then it will load trade "Y" and the same blocks (below) will be applied for "Y".

You can see filters in "For each Trade" itself - you can choose to load only EURUSD, only USDJPY or whatever symbol you want. By default it works with the current symbol only.

Bug, it says that the function is not defined, but it is. I will check what is going on

I just put your v1.5 on a live demo account and it works, I got a trade immediately. You can try to normalize. I think it will work, but create a backup first... or the previous step in the Actions History can be a backup

Hm... what about the lines? They are the same as the orders and trades, but their ticket number is their name. There are blocks to work with objects.

Working with arrays in MQL4/MQL5 is a little nightmare for me, I'm not sure that you want to deal with them

For the "Comment" parameter you can use some variable. Now I don't want to make things more complex because of rare situation like this. And you should be careful with this parameter, because it is very limited. If I remember correctly, only 32 symbols can be used for a comment. Also, it can be set once, then you can't modify it. Which means that you can't put the ticket number there. The broker can always modify it, and I think some brokers actually do that.

The comment is normally changed by the broker when the trade was closed by SL or TP. "[sl]" or "[tp]" is appended in this case. I also use the comment to save information when expiration is used for trades, because they does not support that naturally.

If you have binary options broker, forget about the comment.

You can get the ticket number of course. OrderTicket() always works, but I will recommend to use "For each Trade" with "Not more than..." parameter set to 1, and then use OrderTicket(). Also in the "Condition" block you can find it somewhere in the pink (in loop) category.

What is your situation?

Welcome If nothing else, fxDreema can help you to become more technical about making EAs. I assist everyone, but I prefer if you try it first and then ask about a problem you have. Also, look at the Examples. People say that the documentation of this website is poor and maybe this is true, but also take a look at the Help section.

I need to check if everything is ok with this functionality, but I will suggest to use something else instead of this. For this, I created a big function that collects and calculates data on every tick, which basically makes the EA to run slower on Tester. And also, these statistics are for the global account, they work with all orders, no matter how they were created - by this EA, by other EA or manually.

There are blocks to check if and how many trades/orders are present, better use them. For example "Check trades count".