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

Independence of Charts wrt. Order and Position Display

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

When 'Show Open Positions' and 'Show Active Orders' are ON for a chart, it is possible for the lines displayed to reflect orders and a postion AvgEntryPrice which are the result of automated and/or manual trades/orders placed from OTHER charts.
This occurs whenever there are trades/orders which have been placed from other charts for the same symbol.
It would be desirable, either as the default behavior or as a user-selected option, to be able to have a chart display ONLY those automated and/or manual trades/orders placed from that chart (and not others).
Functionally, implementing this request involves tracking the origin of orders and then having chart display implement a filter that allows only the orders/positions that originated on a chart to be displayed there.

Steps to reproduce this issue

Apply two different strategies to two different charts set to the same symbol.
Or, apply a single strategy with different settings to two different charts set to the same symbol.

Comments (1)
#0
user-offline.png  Harvester (harvester)
Dec 23, 2014 - 07:05

To further add to the above comments... When there are two separate orders on the same instrument, with all of the associated stops and targets, it really can become quite confusing to keep track of things visually.  Keeping each order isolated on each chart would be a very nice touch!

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