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

Instrument Data Range exceeds the specified range

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

Charted data goes back beyound the specified Data Range in Format Instrument window

Steps to reproduce this issue

In Format Instrument window > Settings tab > Data Range
for example for ESM3 contract expiring on 6/21/2013
when selecting Data Range:
100 Days Back from: 6/21/2013 (pinned)
I'm expecting the data to be charted from exactly 100 days before 6/21/2013 which is 3/13/2013 (calculated here: http://jsfiddle.net/V6KKg/1 )
But I'm seeing data charted back from 1/14/2014
This is clearly a bug and it is critical for me because this affects my strategies.

Comments (4)
#0
user-offline.png  orad (orad)
Mar 18, 2013 - 16:14

I'm using: MultiCharts .NET64 Version 8.5 Beta 2 (Build 6527)

#0
user-offline.png  Alex MultiCharts (Alex MultiCharts)
Mar 21, 2013 - 08:02

When you set date to a future one, it will always use current date instead.

#0
user-offline.png  Guest (Guest)
Mar 21, 2013 - 14:28

It would make sense to use current date when the date is NOT pinned. But when the date is PINNED I think it should set it as a fixed date range, regardless of whether it is in future or past.

#0
user-offline.png  orad (orad)
Mar 21, 2013 - 14:32

last message was by orad

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 (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