You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When .goto() method is used, the layout correctly jumps to desired position, however, the legend is not refreshed until mouse moves. For example, if I am at position 1536217800000 with close price at $100, then use .goto(1536216700000), the layout will correctly jump to correct position, but legend will stay at $100 price instead of actual candle hovered by the hairline which should be $86.
Screenshot
Here some step by step screenshots:
I start hovering this candle, which displays a CLOSE price of 6411.84.
Then in my code, I use .goto() to jump some candles behind. It works well, however, look at the legend: it hasn't changed accordingly even though the hairline is correctly positioned.
Code (MVP)
Just trigger a
this.$refs.tvjs.goto(<some_timestamp_here>)
and see the behaviour on screen.
Data Sample
N/A
Console errors (if any)
No errors
Additional Info
tvjs v1.0
Chrome 96.0
The text was updated successfully, but these errors were encountered:
Description
When
.goto()
method is used, the layout correctly jumps to desired position, however, the legend is not refreshed until mouse moves. For example, if I am at position1536217800000
withclose
price at $100, then use.goto(1536216700000)
, the layout will correctly jump to correct position, but legend will stay at $100 price instead of actual candle hovered by the hairline which should be $86.Screenshot
Here some step by step screenshots:
I start hovering this candle, which displays a CLOSE price of 6411.84.
Then in my code, I use
.goto()
to jump some candles behind. It works well, however, look at the legend: it hasn't changed accordingly even though the hairline is correctly positioned.Code (MVP)
Just trigger a
and see the behaviour on screen.
Data Sample
N/A
Console errors (if any)
No errors
Additional Info
tvjs v1.0
Chrome 96.0
The text was updated successfully, but these errors were encountered: