+1 888 340 6572 GET STARTED
MultiCharts Project Management
previous_open_issue.png
Go to the previous open issue
previous_issue.png
Go to the previous issue (open or closed)
star_faded.png
Please log in to bookmark issues
bug_report_small.png
Open Bug report MC-2801

Indicator on multiple timeframe chart breaks after zooming in and resetting chart scale

action_vote_minus_faded.png
2
Votes
action_vote_plus_faded.png
next_issue.png
Go to the next issue (open or closed)
next_open_issue.png
Go to the next open issue
Description

Hello support,

I ran into an issue where I'm using two timeframes (1 day and 1 week) with moving averages (I've seen this behavior with some of my own indicators) based off both timeframes BUT rendered only on the first chart when zooming in and then using the "Reset scales" or the "Reset price scale" menu options to zoom out the indicator based off the second data feed becomes disconnected in terms of price scale and seems to connect it's price scale to the second chart's scale. I should point it that this does not seem to occur when you use the "Zoom out" option to restore the first chart.

Thank you in advance for feedback and looking into the issue - at least the "Zoom out" option seems to be a temporary work around.

Kind regards

Steps to reproduce this issue
  1. Add an instrument based off 1-day data on sub-chart #1 (default)
  2. Add the same instrument based off 1-week data on sub-chart #2
  3. Add 1-line moving average based off 1-day data feed and render it on sub-chart #1 - Y-scaling is "Use same as instrument" without margins
  4. Add 1-line moving average based off 1-week data feed and render it on sub-chart #1 - Y-scaling is "Use same as instrument" without margins
  5. Use the mouse to drag the price scale vertically (up and down) of sub-chart #1, also do the same for sub-chart #2 - you'll see both moving averages scale with the price scale of sub-chart #1 while nothing happens when you size the price scale of sub-chart #2 - this is correct
  6. Zoom into a part of sub-chart #1
  7. Select "Reset scales" option to restore the zoom level
  8. You'll firstly see that the indicator based off the 1-week data goes missing which is an issue
  9. Use the mouse to drag the price scale of sub-chart #1 you'll see that the indicator based off the 1-week data becomes visible, but it is no longer based off the price scale of sub-chart #1, when you drag the mouse on the price scale of sub-chart #2 you'll see that the 1-week moving average now scaled with it even though it is rendered on sub-chart #1 - this is incorrect

Also this corruption of the 1-week moving average remains in the workspace if you save it, if you don't save it after being corrupted you can still salvage it. The "Zoom out" option does seem to not introduce this issue.

Comments (2)
#1
user-offline.png  MultiCharts Support (MultiCharts)
Aug 30, 2022 - 13:13
Hello,

Thank you for the detailed description! However, the behaviour is not reproduced on our end. Could you please join the live chat Monday-Friday from 6:00 AM till 12:00 PM ET to demonstrate it via remote connection?
#2
user-offline.png  Ettienne (et1hugo)
icon_reply.pngAug 30, 18:22, in reply to comment #1


MultiCharts Support wrote:
Hello,

Thank you for the detailed description!
However, the behaviour is not reproduced on our end.
Could you please join the
[[https://messenger.providesupport.com/messenger/tssupport.html|live chat]]
Monday-Friday from 6:00 AM till 12:00 PM ET to demonstrate it via remote
connection?


Sure, I'll check to do a live chat with you tomorrow or Friday.
History
Issue basics
  • Type of issue
    Bug report
  • Category
    Not determined
  • Targeted for
    Not determined
  • Status
    Need Details
  • Priority
    Not determined
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (0)
There are no items
People involved
Times and dates
  • Posted at
  • Last updated
Issue details
  • Reproducability
    Not determined
Attachments (0)
There is nothing attached to this issue
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates