Save $500 with our Black Friday Special – $997 for Lifetime Access! Learn more
+1 888 340 6572
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
feature_request_small.png
Open Feature request MC-947

Aligning the tracker line on sub-second resolution

action_vote_minus_faded.png
4
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

Using the tracker line to compare charts where bars change faster than one second is impossible or extremely difficult. Sub-second alignment is needed for such uses. Please add either millisecond (which probably won't have multiple ticks) or tick-count (which can be used in place of milliseconds when they are unavailable, even if milliseconds are the normal way chosen) based tracker alignment. This sub-second alignment data would also be useful for global mode data playback. 
While you are altering alignment, it would also be good to have the tracker align to the last closed bar instead of the middle of open bars, so that people can do proper historical research without having to go into global data playback mode or figure out each time whether or not the indicators shown have been calculated as of a certain point in time on another window.

Steps to reproduce this issue

Create multiple tick-based charts based on various small numbers of ticks, or renko bars based on small numbers of pips.  Click on a segment where the price is moving quickly (where there are many bars per second).  Notice that it is very difficult or impossible to figure out how the charts align in time.

Comments (0)
History
Issue basics
  • Type of issue
    Feature request
  • Category
    Usability
  • 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
    Normal
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