+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
bug_report_small.png
Open Bug report MC-2033

Volume Profile mis-placed if I have two data series in the chart, for the running chart.

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

Use case: as in pic 1, what I want to achieve is
- data series 1: to show RTH volume profile of NQ for all days
- data series 2: to show overnight volume profile of NQ for only previous day.
This chart setting is because overnight volume profiles do not show important info everyday, but it is only important for previous day.
The pic 1 is before the market start, and it looks like what I wanted it to be.
But after the market opens, as in pic 2, when new volume profiles are plotted, they are plotted mis-placed. I guess the logic of the code is "to plot the new volume profile after the last bar of previous session". This logic is fine only if there is only one data series in the chart. 
I think the logic should be changed to "to plot on the new volume profile on the first bar of current session."

Steps to reproduce this issue

connect to CQG.
set up all "ENQxxxxx" symbols.
set up the overnight session as in the attached picture.
load the workspace attached.
then, let the chart run and wait for it to plot new volume profile when session changes.

Comments (0)
History
Issue basics
  • Type of issue
    Bug report
  • Category
    Usability
  • Targeted for
    MultiCharts 12
  • Status
    Confirmed
  • Priority
    Not determined
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (2)
People involved
Times and dates
  • Posted at
  • Last updated
Issue details
  • Reproducability
    Not determined
  • Severity
    Normal
Attachments (4)
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates