$1000 off on MultiCharts with Advanced Strategy Pack – this Black Friday only! Learn more
+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-1035

Add CQG supported indices (e.g. TICK, TRIN, Nasdaq TRINQ) in data feed

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

In Multicharts 8.0 AMP CQG is a new broker and data feed which is really a great improvement but unfortunately CQG supported indices (www.ampclearing.com/cqg_indexes.html) are not yet accessible though it should not be very time-consuming to also realize the access to those indices in Multicharts. By the way, Ninjatrader does offer access to those indices using their CQG interface. Why does Multicharts make a worse offer to their clients? NinjaTrader bundled in one step all parts of accessible data feeds to their CQG interface and the indices are of value:
 
Some time ago I bought a futures trading system written in EasyLanguage which makes use of TRIN and TRINQ indices, and is has a really great profit factor. Therefore I would be very happy to have access to these indices.
 

Steps to reproduce this issue

Use Multicharts 8.0.5622.401 x64 and try to access one of the CQG indices from within QuoteManager. QuoteManger is only able to add CQG futures symbols and not CQG indices. Even if one tries to manually add CQG indices, QuoteManager will not be able to access the data feed.

Comments (0)
History
Issue basics
  • Type of issue
    Feature request
  • Category
    Not determined
  • Targeted for
    MultiCharts 8.5 (RELEASED)
  • Status
    Released
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 (1)
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates