+1 888 340 6572 Try free for 30 days
MultiCharts Project Management
Go to the previous open issue
Go to the previous issue (open or closed)
Please log in to bookmark issues
Open Feature request MC-293

Tracking Line Alignment

Go to the next issue (open or closed)
Go to the next open issue

When correlating simultaneous events between charts using the tracking line, it would be good to have an option such that the tracking line is on the last CLOSED bar that aligns with the tracked date and time. 
Currently, the line aligns with the whatever bar was open at that date and time. For those of us who want to do historical research of multiple time frames, knowing what value an indicator had on a longer time frame is often important and would be far easier to determine if the tracking line had such functionality. As it stands, the line may align with the NEXT value of the indicator on a longer timeframe, rather than the last/then-current value.

Steps to reproduce this issue

With tracking on and multiple windows in view, one with a shorter timeframe and one with a longer one, move the mouse to a date and time of interest on the shorter time frame that does not align precisely with the closing times of the longer timeframe.  For instance, with the shorter timeframe set on 30min bars and the longer one on 1hr bars, select 1:30 on the shorter timeframe chart.  The tracking line on the hourly chart will be placed on the 2:00 bar, whereas the last closed hourly bar at that time is the 1:00 bar.

Comments (1)
user-offline.png  bowlesj3 (bowlesj3bt)
Jul 27, 2017 - 13:46

This feature may be an even better solution. It is a feature I found in TC2000. Check it out.

Issue basics
  • Type of issue
    Feature request
  • Category
  • Targeted for
    Not determined
  • Status
    Under Review
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (3)
People involved
Times and dates
  • Posted at
  • Last updated
Issue details
  • Resolution
    Not determined
  • Severity
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