+1 888 340 6572
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-1090

Request: Ability to use Simulated Volume Stop order from the DOM

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

I would request the ability to designate stop orders in exit strategies attached to a DOM as simulated volume stops. This way the stop resides on the client computer and triggers only when a certain price AND a volume trigger happens. This feature is in Ninja. It is very useful in manually scalping markets that are not very heavy in volume, where one wants an automatic stop, yet the existance of such stop can adversely influence behaviour of other participants. The volume trigger is an addition that helps staying in the trade in case too few contracts were actually traded in the trigger price. Trading futures for many years I found this feature very useful. Better description can be found in Ninja's docs.
Thanks for considering it.

Steps to reproduce this issue

not relevant

Comments (2)
user-offline.png  chancewebc (chancewebc)
Aug 16, 2012 - 08:18

I also posted a similar feature request
simulated stops is absolutely required for manual trading.
would make multicharts manual trading specialist :)

user-offline.png  MultiCharts Support (MultiCharts)
Feb 12, 2013 - 09:58

Only for DOM?

Issue basics
  • Type of issue
    Feature request
  • Category
  • Targeted for
    Not determined
  • Status
    Under Review
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  tci (tci)
  • Owned by
    Not owned by anyone
  • Assigned to
    Not assigned to anyone
  • Subscribers
    1 subscriber(s)
    Click here to show the list of subscribers
Times and dates
  • Posted at
  • Last updated
Issue details
  • Resolution
    Not determined
  • Severity
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