+1 888 340 6572
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-428

Instrument date ranges do not save in workspace properly

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

When a chart has a date range selected the end date is NOT stored/saved. See bug report - which its seems is deemed expected behaviour.


Please add an option for saving the end date (perhaps in a tick box in the instrument format box) so that end dates can be saved when you are using historical charts that do not require the latest data on them. By default you could have the box unchecked so that users get the current behaviour and you therefore have to select to save the dates as they are entered.

Steps to reproduce this issue

see above bug report

Comments (2)
user-offline.png  JoshM (Jura)
Jun 16, 2011 - 23:47

I agree - this is a annoying missing feature. Since I primarily use MultiCharts for backtesting, I have multiple graphs with different time periods. Now, with MC not saving the end date, every time after start up I have to manually readjust dozens of charts, not to mention wait an extra amount at startup when MC needlessly loads extra data and calculates the strategies and indicators on this data.
I don't think a check box is needed. An even more elegant solution would be to save the end date in the workspace if the end date is less than the current date. Because, if the manually entered end date is less than the current date, the user is using a custom data range and this should thus be saved in the workspace.

user-offline.png  2harriman (2harriman)
Mar 20, 2012 - 23:49

Yes it is really annoying and MC needs to remember the end date

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