+1 888 340 6572 GET STARTED
MultiCharts Project Management
Go to the previous open issue
Go to the previous issue (open or closed)
Please log in to bookmark issues
Open Feature request MC-837

DOM enhancements

Go to the next issue (open or closed)
Go to the next open issue

This PM is a summation of several feature requests listed in this thread ( http://www.multicharts.com/discussion/viewtopic.php?f=1&t=9865 ).
Two of them has already been requested and can be found here ( http://www.multicharts.com/pm/viewissue.php?issue_no=MC-815 ) and here ( http://www.multicharts.com/pm/viewissue.php?issue_no=MC-816 ).
Reviewing them once again, MC-815 requests a clock to be included in the DOM and MC-816 requests a volume profile/cumulative per each price level. Both are considered critical.
X_Trader platform from TT and its DOM has been considered the standard for professional traders. Their volume profile/cumulative is what I'm requesting for MC. Among many features they have one really interesting, but I don't know how it's dependable of the broker. When we send a limit order we see an estimate of our position in the queue, which is helpful to know.
Another thing that should be addressed is the last size traded. At the moment it's presented inside parenthesis right next of the last traded price, but it should have its own column. As we can see in the images presented here, when the number of contracts traded goes above 3 digits, prices letters get smaller. With its own column that won't happened. Also, if we change font size they get outside the cells width. This also must be addressed.
JoshM requested that the Position Size number can be displayed in a non-shaded way.

Steps to reproduce this issue

feature request

Comments (7)
user-offline.png  Michael (Id2)
Mar 06, 2012 - 21:38

integrate Chart and DOM, please check chart/dom from SerriaChart in the link http://www.multicharts.com/discussion/viewtopic.php?f=1&t=9646, when you move your mouse on the DOM, it is pointing to the chart, you can click to send order at any second on the chart. With MC Dom, I have to find out the price on chart, then I turn to DOM to look for the price on the ladder, once I complete the steps, price is gone. 

user-offline.png  Michael (Id2)
Mar 08, 2012 - 09:25
  • one other must have feature is to display highest / lowest price for the curent session.
  • another one would be to link DOMs in groups and have a "center" bouton that would center at the same time all the linked DOMs. (this is critical for anyone usong intermaket relations).
user-offline.png  arnie (arnie)
Mar 16, 2012 - 08:42

Check this video where Ninja DOM is side by side with T4 DOM.
That DOM has also cumultive volume and it's also a good way for MC do go.

user-offline.png  Michael (Id2)
Jun 12, 2012 - 10:52

MC's DOM has in-built 'intelligence' that not everyone wants, and for some of us, it's a downright nuisance.
e.g. When using a Left Click on MC's Dom , an order is placed as a Limit or Stop and is determined by MC based on whether the order is entered above/below the Last Traded Price.
However, other DOMS like OEC's don't do this and allow the user to assign Limit orders to the Left Mouse button and Stop Orders to the right button (or whatever configuration the user prefers). These orders are then submitted with just ONE CLICK and remain as Limit or Stop Orders regardless of where the Last Price traded is at the time of submission.
Why is this important? because if the Ask is at 1310.00 and the Bid is at 1309.75, there is no way in MC's DOM to place a Stop Sell order @ 1309.75 with JUST ONE CLICK if the last price traded is 1310.00.
Unfortunately, we currently have to Right Click and select a Stop order option from a drop down list (too slow and cumbersome). A left Click on 1309.75 in the above example submits a Limit order which is filled immediately. That may not be what is desired if the Last Price traded is 1310.00 and we want to wait for the market to downtick before we are entered rather than being the one who causes the downtick.
I know that Tradestation does it the MC way but all the other, better DOM's, like OEC, TT and J-Trader do not. At the very least there should be an option provided to choose how the buttons are configured. We discussed this ages ago and I was told that such an option would be provided. To date, it still has not. Could it be included during this revamp - please!

user-offline.png  stocksbaron (stocksbaron)
Jul 30, 2013 - 23:38

Someone noted before me that the DOM should be extended to make it more like the way it works in TradeStation. It is very handy there to :
1) Have multiple DOMs open, one for each traded instrument.
2) Be able to see P&L as well as the stops and targets in each, and to be able to adjust them as necessary. 
Hope this makes it into the next version & keep up the good work!

user-offline.png  Michael (Id2)
Sep 24, 2013 - 05:47

Some other enhancements for the DOM:
1) Allow the ability to use it in market replay. Any trader who trades using the DOM is going to want to practice using the DOM too.
2) Allow the ability to rescale. Currently with something like Forex on LMAX, the scale is one tenth of a pip, which means the entire DOM will only cover a few pips. If you could allow customisation so that the DOM shows every half pip, or every two tenths of a pip for example that would be easier.
3) Find a way to allow faster scrolling up and down the ladder.

user-offline.png  MultiCharts Support (MultiCharts)
Jul 30, 2015 - 10:00

Volume profile/cumulative per each price level has been added in MultiCharts 9.1 Beta 1.

Issue basics
  • Type of issue
    Feature request
  • Category
  • Targeted for
    MultiCharts 9.1 (RELEASED)
  • Status
    Partially Implemented
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (3)
People involved
  • Posted by
    user-offline.png  arnie (arnie)
  • 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
Attachments (4)
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates