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

Ability to Choose: Timestamp of Bars based on "Open" or "Close" of bar

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

Issue:
It is currently understood the MC's chart timestamp is based on "Close" of bar.

It means that the bar that is open, for example, at 15:58 and closed at 15:59, will acquire the 15:59 time.
This is hard coded and cannot be changed.

However many other platforms (i.e. Thinkorswim, TradingViews) uses "open" of bar for their timestamp.

This difference of timestamp setup will result significant chart difference, especially with larger and larger intraday time intervals (i.e. 30min, 1h, 4h, 8h). And due to significant chart difference between other platforms, the indicators/signals/strategies will result very differently.

Feature Request:
An option to let MC user to select to use either "Open" or "Close" of bar for chart timestamp at program level will be very beneficial. If use decided to change from "Close" to "Open", entire MC programs must be shutdown and than restarted for it to take effect.

Comments (0)
There are no comments
History
Issue basics
  • Type of issue
    Feature request
  • Category
    Not determined
  • Targeted for
    Not determined
  • Status
    Under Review
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (0)
There are no items
People involved
  • Posted by
    user-offline.png  rc76 (rc76)
  • Owned by
    Not owned by anyone
  • Assigned to
    Not assigned to anyone
  • Subscribers
    1 subscriber(s)
    Click here to show the list of subscribers
Times and dates
  • Posted at
  • Last updated
Issue details
  • Resolution
    Not determined
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