+1 888 340 6572 GET STARTED
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-741

Make the InsideBidSize and InsideAskSize available in PowerLanguage

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

Make the size of the InsideBid and InsideAsk available as a PowerLanguage reserved word, so that automated trading strategies can retrieve the best bid and best ask size before placing an order.

This feature request is somewhat related to issue 520, which is a request for orderbook availability, but which also deals with storing and exporting this data (which is this issue is not about):

http://www.multicharts.com/pm/viewissue.php?issue_no=MC-520

Steps to reproduce this issue

n/a

Comments (2)
#0
user-offline.png  GB (Id2)
Aug 28, 2012 - 22:04

Another disappointment today during the trial. Have written the code using IB then subscribed to IQFeed for more ticking instruments and... it comes out that DOM_ functions dont' work with IQFeed, only with brokers.
Please make InsideBidSize and InsideAskSize available in nearest release. Meanwhile I am off to a different platform.

#0
user-offline.png  MultiCharts Support (MultiCharts)
Jul 28, 2015 - 15:31

AskSize, BidSize, q_AskSize, q_BidSize are now supported

History
Issue basics
  • Type of issue
    Feature request
  • Category
    Usability
  • Targeted for
    MultiCharts 9.1 (RELEASED)
  • Status
    Released
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (3)
People involved
Times and dates
  • Posted at
  • Last updated
Issue details
  • Resolution
    Not determined
  • Severity
    Critical
Attachments (1)
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates