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

Dividers within Inputs

action_vote_minus_faded.png
6
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

Hi,
I would like to see a feature where by in the EL code inputs: section, I could define some dividers between groups of inputs.
These dividers would then be displayed when altering the Study inputs and during modification of the inputs in the optimizing area. At the moemen, I create dummy inputs ie System_Exits("== In Points/Pips ==") this is displayed OK when formating signals but in the optimization section, you can't optimize a string so this line is left out. Thus losing all of my dividers.
Neil.

Steps to reproduce this issue

It's a request

Comments (1)
#1
user-offline.png  gkiff (gkiff)
Oct 11, 2019 - 16:14

I would go further than this and allow all inputs to be categorized, then on the signal inputs and optimization screens, the inputs could be shown by category.

Maybe even having a user preference to show inputs:
unsorted
sorted (alphabetically)
categorized

In terms of MC.net, it would be as simple as defining your inputs as:
[Input("NameOfCategory")]
public double StopLossPcnt {get; set; }

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
  • Posted by
    user-offline.png  NW27 (NW27)
  • Owned by
    Not owned by anyone
  • Assigned to
    Not assigned to anyone
  • Subscribers
    2 subscriber(s)
    Click here to show the list of subscribers
Times and dates
  • Posted at
  • Last updated
Issue details
  • Resolution
    Not determined
  • Severity
    Normal
Attachments (2)
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates