Or why not directly using this symbol http://prntscr.com/409qzx 😕

____I was reported about the "New order error" and I fixed it. It has nothing to do with the other warnings, but I will check those warnings anyway, I don't like warnings about arrays :)[/quote:26wq2en0]
Thanx FxDreema.
Because I cannot compile and test properly any EA since that problem.[/quote:26wq2en0]
Thank you. The compilation is working properly now.

Wow, this is new to me, I never used this option in forums 😄 But i guess this is the answer: ucp.php?i=main&mode=bookmarks

I can't open .ex4 file with fxDreema 🙂

Optimize the EA? If it is one parameter, or few of them, use these checkboxes to make that parameter input parameter for the EA: http://prntscr.com/3ysxd6
Otherwise you can create Constants, which are also input parameters, and use one Constant in multiple blocks, and optimize the EA on it.

http://docs.mql4.com/strings/stringfind
What do you want to do?

Thanks very much.

Indicators gives the EA values, if those values are similar - ok, it can be done easily. Otherwise there is no something like automatically formatting MAs in a way to look like they cross while they are 1000s of pips away from each other, and that number even changes depending on the time window perion where you are looking at. But if there is some custom indicator that does something similar, it can be used.

If you made the same project in the web version I will be able to see it and tell you exactly what is going on. It can be imported also from .mq4 file (the one generated with fxDreema).

https://fxdreema.com/shared/pPFbJGAxd

Sometimes I play with fxDreema trying some simple strategies, mostly for fun. The history data is crap, but what can I say 🙂

For the EA indicators are only numeric values. Bollinger is similar to MA, so it is possible to cross them or anything else that you can do between two MAs or two Bollingers

Thank you very much. Worked perfectly. Much appreciated

Practically this is the same thing, the same event.

Many people ask for candle close, and let's say that this is something that happens on the last second of our timeframe. But there is a problem with it. MetaTrader has this "On Tick" event and the EA reacts on it, but it does not have "On Candle Close" event. Well, we can make it by creating endless loop and waiting for the second to become 59 and fire that even (call some function), but this is possible in live only. When backtesting, the EA is controlled by this "On Tick" event and it only does something when a new tick is "received". But ticks are irregular, some can come in :58, the next can come in :59, so how can we know from inside the EA which tick will be the last tick of the current candle? I don't know how. And if we create some endless loop and backtest it, the EA actually stops on it, it stays forever in the same tick.

So... "Once per bar" when placed under "on Tick" does the job to detect the moment when a new candle is created. Yes, it can be few seconds in the new minute, but it's pretty accurate and works well 🙂 So my suggestion is to place the "Close" block before "Buy" or "Sell" one.

OK. Sorry. It's solved.
Yes, I'm using a custom block....the problem was a "indicator Rise/Fail" block...it was with "pass once per bar" parameter selected....that was the problem.

Thanks!

I see the difference 🙂

Normally you check past indicator data. Click on "More settings" and you will see Candle ID there. This is at which candle you want to get value. 1 = previous candle. 2 = prev. to previous. And so on... positive values means that you are going past into the history. Here is some info: https://fxdreema.com/documentation/gett ... indicators

So it is the opposite of what you are thinking. Instead of looking at conditions now and say "I want to buy after 30 minutes", at the current time you are looking 30 minutes back to see what were the conditions. This is how normally EAs are made.

Hey dreema! Took a peek at the screenshot, awesome. That narrows down the bugs a little bit. Still not executing quite where I want it to (it should be executing the MG trade type after the BU trade type records a loss). I will poke around with it some more!

Thanks for your time 🙂

Well, the closed trade has "parent" trade even if you close it for the last time. To resolve the problem I added function to get the "child" ticket, so now there are 2 checks. I think purple blocks are enough 🙂

Haha yes. The reason is that the Condition block is a little bit locked... when I have to change something in it I need to change many other things as well, so I don't even want to think about this 😆 Otherwise this request is not something new, it's from the very beginning. But on the other hand when you have 1 block per condition, all conditions are clearly visible... ok, this does not sound very convincing 😆