Possible bug in positioning candle in 'future' candles
-
https://fxdreema.com/shared/UYvk6RUhe
@fxDreema @miro1360 after cracking my little pea brain and managed to get this thing up: dont ask me how this does but hoping this would allow me to guess when is the turning point for a trend. so, using on historical candle works fine but when i tries to use it on my recent candle (say candle 7) and those calculation (current candle minus 9, -18, -26 etc) into the future candles (eg -1, -2 ~ -26 aka shift forward) cannot show those lines.
read the solution from miro1360's to somebody's post on similar, miro1360 uses 'shift in time' function to push to 'future' and but i can be using 1 set for 'future' line and and 1 set for historical line...
i think the big fxdreema BOSS can think of a way... no other software can do it... only fxdreema can and that's why i stick with fxdreema... please boss.. make it work, okie?? thanks!!
-
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(). -
@fxdreema you should make a sticky post in all forum categories:
"How to ask for help
- what have you tried
- what is the goal
- the problem in most simple form
- etc.
otherwise support is not guaranteed. "
Edit: I'm referring to this lol
-
It does not seem difficult to answer this post of August 24, it's just one of many......
-
@roar said in Possible bug in positioning candle in 'future' candles:
@fxdreema you should make a sticky post in all forum categories:
"How to ask for help
- what have you tried
- what is the goal
- the problem in most simple form
- etc.
otherwise support is not guaranteed. "
Edit: I'm referring to this lol
I support the motion.
-
hijacking my post haha
-
@vnpython-0 said in Possible bug in positioning candle in 'future' candles:
hijacking my post haha
No. Just supporting it! LOL

-
@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:
and cant draw line on both historical data and future data... @fxdreema please help?