Honestly, I'm not an expert on this block :/.

@fxdreema said in Possible bug in positioning candle in 'future' candles:

I tried this: https://fxdreema.com/shared/OuUNxlf3d And I got an error "array out of range" when the EA tried to get value from future candle. It's because there is no data about the future candle, it doesn't exist. I believe that the Time attribute is like Open, High, Close, Low and Volume, it's connected with the candle, and with no candle there are no attributes.

You can get the time of the current candle, because that time is rounded, and add seconds to it. The time is the number of seconds since 1.1.1970. Look at this: https://www.epochconverter.com/ The "Comment" block may draw human readable version of the time, but in reality it is an integer number.

Here is another example: https://fxdreema.com/shared/wreYKAEL
I use that "shift in time" feature, but instead of using fixed number of minutes, I use Period(). It returns the number of minutes for the current period. If the period is M15, it returns 15. So that way you can put the EA on different period and it will show you the time of the non-existent future candle. You can use 1 * Period() or 2 * Period() or MyVariable * Period(). Even _Period should work instead of Period().

i just tried on draw vertical line on Period() as per your 'comment' block but on 'draw line' block: 0_1572963836008_3bd04fa4-9842-4369-a6f6-ec194341fabd-image.png and cant draw line on both historical data and future data... @fxdreema please help?

@l-andorrà That seems to be an actual bug in the builder, I can do nothing but hope the admin fixes it...

@gsmtricks Just replace it to the function:
MathFloor(Rate * 100) / 100

Hope it works!

Permíteme dos preguntas previas. ¿Lo estás probando en mq5? ¿En qué ocasiones funciona y en otras no?

I'm getting that one also but the good thing is that there are no more hundreds of compile errors like there used to be.

It happened to me at least twice. I guess (and it's just a guess) that when a block including a variable is deleted BEFORE its variable was removed it becomes a kind of 'ghost' that is not visible on the builder bit it is still considered to be in the project.

I had to redo the whole project to fix that problem. 😞

@serioza i forgot, this is not a bug

What pip rules are being applied? I guess that '-.01' is the reason when nor properly matched to pips rules. If you are using those by default, you should need to insert '-1pips' (the word pips included) on that field.

If I remove that (symbol) it compiles and seem to work, but who knows if influence EA and how

@trader-philipps thanks.. it was the spread difference. I was using "current" and with the market currently closed and not trading my results were off. I switched the spread and now everything works fine. Thanks

@casebefx Can't reproduce. Maybe a browser specific or caching issue. Have you tried with browser in private mode? Are you connected through a proxy server?

I recommend you to contact the administrator directly via the support page.

@l-andorrà That also happens on mq4 projects. I spend hours once to find my error in metaeditor as it wouldn't compile.
If I remember correctly in my case I left blank the fixed SL and changed to risk percent. That always didn't compile due to zero divide.

Before I knew the reason I fixed it by recursively deleting blocks and create them again.

I managed to find a different solution. I'll just keep this topic here, eventually the admin/programmer will read this and have a look at this bug.

Thanks for your time.

Ok. Thanks. Only you will receive his answer. Could you please share it in the forum once confirmed?

@sirboyce Are you sure that if you compile in Meta Editor there are no errors reported? May you send a project link that we can have a look?

@trader-philipps said in about 'Check type (last loser) (last winner)' stopping trade:

@l-andorrà Eagle eyes again .. respect!

LOL... 😄

@nikolas_m_s Tick data may be the issue. You may have different results with 2 instances of MT on a single PC.