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

Please add a way to select Time Zone from Format Instrument's Data Range section

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

Today's Date : 2012/09/21
PC's timezone setting : GMT+9(Seoul, Korea)
IB's NKZ12 symbol is from SGX and SGX's timezone : GMT+8(Singapre)
NKZ12's Session modified from QM : 00:00-23:59
I want to plot IB's NKZ12 symbol (1 min chart) with 1 Day Back or From(2012/09/21)-To(2012/09/21) based on SGX timezone, not local timezone.
Format Symbol's Time Zone for Display : Exchange
Format Symbol's Data Range : 1 Day Back or From(2012/09/21)-To(2012/09/21)
 
The NKZ12 chart's first bar timestamp is 2012/09/20 23:00:01, not 2012/09/21 00:01:00.
The display timezone is Exchange, but the loaded data range is local.
I want both to be Exchange based. 
This is because the Format Instrument's Data Range always refers to local timezone.
We need to set the Data Range based on Exchange and GMT too.
 
So, please add a combo box for selecting timezone from Data Range as we have one from Display.
 

Steps to reproduce this issue

Follow the above Issue Description
 

Comments (0)
There are no comments
History
Issue basics
  • Type of issue
    Feature request
  • Category
    Usability
  • Targeted for
    Not determined
  • Status
    Not Reviewed
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
  • 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