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-704

Display the correct currency symbol for P/L of open positions on charts/chart trader

action_vote_minus_faded.png
4
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 the P/L of open positions is always displayed on charts/chart trader in connection with the "$"-currency symbol even if the underlying currency of the instrument is different and though the P/L value belongs to the instrument's currency.
Examples are the German FDAX future contract, or the FX pairs EUR/GBP, EUR/JPY.

Maybe You can add an option in QuoteManager for the "Edit Symbol" dialog box to be able to select the currency of the underlying instrument. At least the following currencies should be selectable: USD ($), EURO (€), Yen, British Pound. The corresponding currency symbol should then be displayed for the open profit/loss of that contract.

By the way, I tested the "Multicharts powered by LMAX" version of Multicharts and I saw that there the correct currency symbol is always used. Why is it not possible in 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
    Usability
  • Targeted for
    MultiCharts 8.8 (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