Celebrate Independence Day with MultiCharts! Get super low prices
+1 888 340 6572 Try free for 30 days
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-2003

Add an instant BE (breakeven) button to main interface of DOM

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

At the moment we have a breakeven strategy and a master strategy that includes some form of breakeven positioning.
I would like a button actually on the DOM itself that immediately moved the stop to breakeven (+ whatever ticks would cover commission).
This would match competitor DOMs such as that provided by SierraChart.

It would be very useful and increase performance in fast moving markets where the hypothesis for your trade can become invalidated very quickly and you need to move quickly to ensure you are protected but not necessarily exit the trade immediately

Steps to reproduce this issue

If you are in a trade and slightly ahead but then your reason for entering the trade is invalidated it takes several seconds to add the breakeven strategy to your open position, especially if the price you entered on is not currently within the DOM visible price range on the screen (ie it is much harder to drag the BE strategy onto the open position in this circumstance).

If you had an instantaneous button it would dramatically reduce the time taken to protect your capital in that scenario.

Comments (0)
There are no comments
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