We are happy to announce the MultiCharts Easter Sale! 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-702

Don't use average entry price for open positions

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

I already explained in MC-582 that a change in the current order management is desireable. I want to give two examples in which the current order management results in unexpected behaviour:
a)
I used the chart trader panel to buy one contract without any exit strategy. The open position was displayed on the chart. After some minutes I chose the "Stop Loss" exit strategy and activated it on the chart trader panel. Finally I used once again the "Buy Mkt" button to buy another contract of the same instrument. Now the chart displayed the average price of both contracts as entry price for both contracts and one stop loss order for both contracts below the average entry price in the predefined distance from the entry price. However I would expect that the stop loss order is only placed for one contract and exactly in the predefined distance from the entry price of the secondly bought contract. 
b)
Imagine that the first contract was bought without any exit strategy (maybe a long term trade). After some time the current price felt 30 points below the entry price of the first contract. Now one wants to enter a shot term trade and uses a stop loss strategy which places a stop loss 10 points below the entry price. After the order is places by a "Buy Mkt" order and executed at a price 30 points below the first entry price, MCDT computes the average entry price to be 15 points above the current price and places a stop loss exit strategy 10 points below the average entry price for both contracts. Now as the average entry price is 15 points above the current price, the stop loss is placed 5 points above the current price and what happens is that the stop loss is executed immediately! That is not an expected behaviour and it should be changed!
 
I want to suggest a completely different order managemant at this point: Each open position should be displayed on the chart at it's entry price and not all open positions at an average entry price. Each dependent OCO order or other exit strategy should always be corresponding to the entry price of it's open position. When an open position is closed by the "X" on the chart only it's corresponding orders should be cancelled an no other orders. That is the only way how pyramiding can be made possible in MCDT and I already use other platforms which offer such a feature. Of course, if someone consecutively opens many positions of a contract at different entry prices it can happen that the chart is cluttered by open positions and dependent orders but it is the most precise way to handle order management. At least there should be an option to use such a precise order management on a chart. It would be of much value for me and probably for many other traders. Finally, it is the only way to handle orders in the case Multicharts wants to support hedging in future releases of MC/MCDT.
 

Steps to reproduce this issue

Use MCDT 7.1.70.201 Beta 1 on a PC with Windows XP Professional SP3 and Open E Cry demo  account.
 

Comments (0)
History
Issue basics
  • Type of issue
    Feature request
  • Category
    Not determined
  • Targeted for
    MultiCharts 8.7 (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 (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