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

Support custom futures in DOM

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 using custom future on the chart, you can not use this in the DOM. You will get no data. To use the DOM to trade what is on the chart, you can use the current contract of the custom future to get data. This has some implications for the information shown in the DOM.
For instance: when you apply exit strategies with the chart trader, not all the info on the chart is also on the DOM (trigger levels for instance). Also strategies taking with the DOM, can only be cancelled with the DOM and vice versa with the chart trader. For example. When applying a master exit strategy with the DOM. If you want to cancel the targets, you have to do this with the DOM.
Solution would be to support custom future in the DOM and link the symbolmapping (what is already done for the chart) to the individual contract for the DOM also.
This is discussed in the following thread:

http://www.multicharts.com/discussion/viewtopic.php?f=1&t=46527

Steps to reproduce this issue

Feature request.

Comments (0)
There are no comments
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
  • Posted by
    user-offline.png  evdl (evdl)
  • 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 (1)
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates