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

Pip definition when using 1/10 pip broker

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

MC considers the value of a pip as the last digit after the decimal point, which is absolutely false when the data are expressed with a precision of 1 / 10 pip.
Consequently, all functions using the concept of pip, are all unusable.

Steps to reproduce this issue

Use a broker / data provider with 1/10 pip data

Create a chart using a resolution in points, then you have to multiply by 10 the initial value of the desired resolution. Example: You want a resolution of 10 points, then you need to enter 100 points to obtain a real 10 points graph...

Enter a trade position and then attach an 'Exit Strategy' (Master Strategy, Stop Loss, Profit Target, etc...) that you want to set in pips, then you must multiply the number of pips per 10. Example: You want to attach a Stop Loss strategy with a value of 30 pips, so you need to enter 300 pips...
And if you enter 30 pips, then your Stop Loss will be executed at 3 pips

Enter a trade position and the go to Order & Position Tracker in order to 'Change Limit Price'. You will see that "+1 Pip" is actually '+0,1 pip', which is not usable.

Etc, etc, etc, ...

Comments (2)
user-offline.png  Nick (Nick)
May 24, 2011 - 04:49

Just wondered how this can be anything other than critical? Studies just do not work at all on spot FX with this bug.

Issue basics
  • Type of issue
    Feature request
  • Category
    Not determined
  • Targeted for
    MultiCharts 7.0 (RELEASED)
  • Status
    Partially Implemented
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 (3)
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates