Topics created by moreirajbn

@miro1360

Excellent Miro...

I got the concept... my problem was with the initial code. 🙂

Thanks a lot again.

@wagner
0_1553452554412_35c0bdd5-db5c-4393-a3ad-27db291fe047-image.png

Interesting. This function iBars was not present in MQL5 as long as I know and that's why I defined it. On the server the compiler I use is a bit older and that's why it works. On your PC MetaTrader is the newest version and maybe they added this function lately, although I can't find anything about it in the documentation.

@fxdreema

The thing is that there are ticks... there are no deals, but as I understand MT5 considers a "tick" as anything that changes the bid/ask spread or the last deal in the market. So in circuit breakers we see changes in bid/ask, but without any deals, just by placement and cancellations of orders on the order book.... so it's quite different from Forex, where brokers make their own bid/ask spread and decide when it's time to change it.

The mess gets really ugly on the CFDs, that trade through the broker's own bid/ask, but are arbitraged by the broker's market markers on the centralised markets. So when there is a circuit breaker on the exchange where, let's say Apple stocks are traded, the Apple CFDs will get REAAAAALY ugly...

Anyways, thanks for the help.

0_1526931055133_miro1360_test2_1.0.mq4

0_1526931077450_97527763-c83e-4862-9e85-d7287bf46c49-image.png

@fxdreema

I agree that there is no golden rule on how martingale should work. In my opinion the EA should look at the lot size and overall outcome (profit/loss) of the previous position, independently of how it was open (market or pending order) to decide on the next pending order's lot size, but this is just my opinion.

Either way, now that the function is working (I've tested a "simple martingale" from pending orders at least) the user can see how the block behaves and decide for himself what to do...

As always, fxDreema empowering trader's creativity... best tool on the whole internet 🙂

Miro, you are a pro 🙂 I would say that this is a job for some custom indicator or a custom block.

fxDreema fixed it really fast.... 🙂
thanks

@miro1360

Awesome, thanks so much.... works perfectly now.

I've been struggling with that for hours because the alternative solution is to use the "Delay" block, but for this block to work on the backtest, MT5 must open a .dll file and that was making the backtest intolerably slow (i.e. minutes to run a week on OHLC).

now it runs perfectly and super-fast 🙂

thanks again