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

Add BidSize and AskSize on Trade Bar
action_vote_minus_faded.png
13
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

Currently Trade Bar does only display the last price permanently and offers to display Bid and Ask values after clicking on the arrow on the right sight of the last price. My feature request has two parts:
1) Display of BidSize and AskSize of the chosen instrument on the Trade Bar.
2) Make Bid, Ask, BidSize, and AskSize permanently viewable on the Trade Bar.
 
Before someone makes a trade decision these values are always very important as they have much influence on the trade transaction at the broker.
By the way, NinjaTrader has implemented a Trade Bar which shows these values permanently.
 

Steps to reproduce this issue

Use MultiCharts DT 7.0 Beta 3.

Comments (1)
icon-mono-settings.png
#0
user-offline.png whammer (whammer)
May 15, 2011 - 17:57

I agree that the lack of bidsize and asksiize information is gap that can be easily filled. I was not aware if this post and requested below that bidsize and asksize be added as keywords to be used in indicators and strategies.  issue MC-347

History
sidebar_collapse.png sidebar_expand.png
Issue basics
  • Type of issue
    Feature request
  • Category
    Usability
  • Targeted for
    MultiCharts 14 (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
    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