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

Each opened position should be displayed at the price level at which it was filled

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

I offen use pyramiding. That means, that I open a position in one direction, and after some time when the trade is already profitable, I decide to add some contracts to the already existing positions (same direction). Unfortunately, when I do that in MCDT, the chart only displays one open position at the average price of the positions at which I originally opened the positions. If I now want to close the lastly opened position because I see that I entered the trade at the wrong price level (market goes against me), I am not able to do that on the chart as the chart only displays one position at the average price. That is a really unflexible handicap, and I want to request an option for chart trading such that each opened position is displayed at the price level at which it was filled, and such that each opened position can be closed seperately on the chart (together with dependent stop and limit orders). By the way, I already use such a feature in another trading software.
The feature is also required in the case Multicharts wants to support hedging accounts where open positions can exist in both directions but currently I am only interested in pyramiding and for it the feature is necessary, too.

Steps to reproduce this issue

Use MCDT (final release from 15.07.2011).

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