+1 888 340 6572 GET STARTED
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-861

Session Break line not shown on the session end time, but on the last tick time

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

See the attached and the answer from the support was
At the moment session break line is plotted on the last bar of the session itself.
If you want to plot session break according to the time stamp (e.g. 16:30) then please submit a feature request to the Project Management of our web site so other users can vote for it: 
It would be better having an option to select wheter to display the session break either on the last bar or on the session end time.  Default behaviour better be the latter.
Below is my original email about this issue.
SessionBreakNotSynched.png shows 4 data series:
- 10199000
- usd999
- ksetrend_f_at
- ksetrend_f_bt
All these 4 symbols are from the same exchange, share the same session
hours (09:00-16:30) and all 1 min series.
Two upper series and two lower series display session break lines which do
not synch. Checking QM data reveals that the session break lines are
displayed at the time of the last min data, not the end of session.
Shouldn't they display at the end of session hours?
Please let me know how to make the session break lines synch at 16:30.

Steps to reproduce this issue

Plot any series which will have the last tick before the session end time.
The session break will be shown on the last tick not the session end time.

Comments (0)
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 (3)
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates