+1 888 340 6572
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-1856

Alternate Labels for SetStopLoss() Exits

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

I'd like to request a feature that allows the currently hard-coded on-chart label of "Stop Loss" (as used for any exit triggered by the SetStopLoss() keyword) to be changed programatically via a 2nd parameter to SetStopLoss(), or by the programmatic setting of a new option for what the text should be at any given point.
To understand why, please observe the attached chart.
You will see, visually,  a breakeven stop, a trailing stop, and a stop out.   These have all be implemented via the keyword SetStopLoss(), but they are logically different and it would be good to be able to have them labeled differently on the chart if/when desired.
Aside:  the implementation uses positive, negative, and zero values for the current single dollar-oriented parameter to SetStopLoss().
The reason why all these different exits must be implemented via SetStopLoss() is that this is the only way to avoid having multiple orders and therefore multiplied margin requirements (often leading to order rejection) sent to the market.
Although it requires serpentine wizard-code to accomplish it (), the single-keyword implementation does seem to solve the problem (so far at least), and it is a very important problem for real traders to have solved.

Steps to reproduce this issue

N/A.  Feature request.

Comments (1)
user-offline.png  MC_Prog (MC_Prog)
May 01, 2015 - 14:21

Being able to re-label the exits would allow the user to easily see which part of the exits code was responsible for causing the exit to take place where it did.

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 (1)
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates