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

Make Exit Strategy parameters on Chart Trader panel local instead of global

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

Currently, when I select a profit target or stop loss exit strategy on two or more charts simultaniously, and change for example the number of ticks for a stop loss exit strategy on one chart trader panel the value for the number of ticks for the stop loss exit strategy on all other charts is changed, too. That is a bad behaviour as the number of ticks for a stop loss is normally selected based on the individual instrument and personal liking. The number of ticks should not necessarily be the same on each chart. It should be a local and not gobal variable on each chart.

Steps to reproduce this issue

Use Multicharts 8.5 x64, open two charts with different instruments, and on both open the chart trader panel. Select on both chart trader panels a stop loss exit strategy. Edit the stop loss exit strategy on the first chart trader panel. Change the value of ticks to 20 and click on "Save". Now edit the stop exit strategy on the second chart trader panel, change the value of ticks to 10 and click on "Save" again. Finally, edit the stop loss exit strategy on the first chart trader panel once again. Now You can see that the value of ticks is 10 here, too, though You selected 20 ticks before.

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