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

cannot change functions 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

From easy language it is very easy to change indicators data series, such as:
spreadPrice = DataSeries1 - DataSeries2;
(On chart, opened two products, and have dataseries1, dataseries2)
spreadPrice is created by user.
StdCal = StandardDev( spreadPrice , Length, 1 ) ;
BUT, on powerlanguage, there is no way can change the dataseries to spreadPrice series.
Since if when you create "new VolatilityStdDev(this, 2);", the second parameter only accept 1 or 2, which means only accept dataseries1, dataseries2, which already opened in charts. But cannot accept my new created spreadPrice as 3.
And there is no filed to change the dataseries like averageFC does, averageFC can use m_AverageFC.price = newdataseries; But VolatilityStdDev cannot.

Steps to reproduce this issue

Every function add feature to change dataseries to the one user new created, 2 ways:
1. allow the second parameter "int data_stream" point to the new created dataseries, while not restrict to the opened products in charts.
2. add a function to change dataseries such as averageFC does: m_AverageFC.price = newdataseries;

Comments (0)
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