+1 888 340 6572 GET STARTED
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-1819

Allow annotation of study inputs

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

This feature consists of two things:
1. Allow use of Description attribute on indicator/study inputs.
[Description("Number of bars in a fast moving period")]
public int fastLength { get; set; }
2. Show the description in the Format Indicator or Format Signal window.
It would be great to also support a similar thing in MultiCharts PL especially since your indicators can be in compiled format with no access to source code, these annotations will come extremely useful both for developers and users.
See: http://msdn.microsoft.com/en-us/library/System.ComponentModel.DescriptionAttribute

Steps to reproduce this issue
  1. Open Format Indicator or Format Signal window.
  2. Select an input
  3. There is no description for the input
Comments (2)
user-offline.png  orad (orad)
Dec 21, 2014 - 03:36

More attributes from the System.ComponentModel namespace can be used here. For example instead of always showing the identifier name for Inputs, we could use the [DisplayName] attribute to show custom names. This allows using spaces in input names, for example "Some Input Name Alpha" instead of "SomeInputNameAlpha".

user-offline.png  orad (orad)
Apr 27, 2017 - 07:34

This would be useful and should be easy to implement. Please review this suggestion.

Issue basics
  • Type of issue
    Feature request
  • Category
  • 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
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