+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-156

Ticks Sequencing ID

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

ticks are saved in the database in the same sequence as they were received and you can recall tick data in the correct sequence if you use one data series on your chart.
However, if you plot several data series on the same chart synchronized with each other, there is no way to know in which order they should be placed - they can all come in one second.

Steps to reproduce this issue

The solution is to use sequencing ID and millisecond or microsecond granularity.

Comments (1)
#0
user-offline.png  CrazyNasdaq (CrazyNasdaq)
Feb 06, 2011 - 10:49

Glad to know that you have choosen my solution posted here in the forum at Post #5 http://www.multicharts.com/discussion/viewtopic.php?f=1&t=8116  or here in Traderslaboratory in October 2010   http://www.traderslaboratory.com/forums/34/time-sales-profile-indicator-8682-2.html#post107012

History
Issue basics
  • Type of issue
    Feature request
  • Category
    Usability
  • Targeted for
    MultiCharts 7.0 (RELEASED)
  • Status
    Released
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (3)
People involved
  • Posted by
    user-offline.png  Dave (Dave)
  • Owned by
    Not owned by anyone
  • Assigned to
    Not assigned to anyone
  • Subscribers
    2 subscriber(s)
    Click here to show the list of subscribers
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