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

Need a way to tie array elements to a particular data series

action_vote_minus_faded.png
4
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 working with multiple data series, it is often convenient to apply the same algorithm to multiple data series and often it necessary to access past values of that operation. Therefore, to minimize coding redundancy and tedium , it would be very useful to be able to tie individuals elements of arrays to a particular data series as can be done with individual variables now. It would be even better if the setting of series could be done using "data(N)" rather than having to use "dataN", even if it had to be done in a "once begin ... end" block. Could MultiCharts please have this ability added? As it stands now a custom DLL has to be used to do this, and function call like "GetArrayElement(variableID, dataseries, barsAgo)" is far harder to grep than "variableID[dataseries][barsAgo]".

Steps to reproduce this issue

Try to code a signal that applies the same methods to multiple dataseries and then compares results of the various data series against each other and notice how extremely tedious it is.

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