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

Data Number of a instrument can't be changed after removing a data series

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

When using multiple data series (> 2), and removing one from these, the data series number (defined in the Format Instrument -> Settings -> Data Number) can not be manually changed.

For example, if you calculate a strategy or indicator on four data series, and remove the second, the other data series will hold the numbers 1, 3, and 4. Now, multiple annoying things happen.

First, you'll get an error popup saying that Data 2 is missing. But because you can't manually change data 3 to data 2, and data 4 to data 3, you'll need to delete Data 3 and Data 4, then re-add each of them, and then turn on the indicators and signals that got turned off by the error popup.

It would be a lot easier if we can change the Data Number in the Format Instrument -> Settings screen, so that we don't need to manually remove each data series and then reapply it. That would be quite an time saver.

Steps to reproduce this issue

See description and attached image.

Comments (0)
History
Issue basics
  • Type of issue
    Feature request
  • Category
    Usability
  • 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
    Low
Attachments (1)
  • /pm/public/files/show/295
    Example of the inability to change the data series number uploaded Nov 05, 2011 by JoshM (Jura)
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates