MultiCharts Easter Sale has jumped in! Up to 50% off Explore offers
+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-1552 » Open Feature request MC-1331

Renko base price

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

ISSUE:
The last digits of open and close of the Renko boxes are dependent of the fist open of the chart chart. Chart and studies change when you modify the beginning date of the chart.

Example:
first open of a EURUSD chart =1.30176 ( with box size=0.00010 ) ==> all the open and close prices end by "6"
if I choose an other date for the chart beginning we have:
first open of a EURUSD chart =1.30491 ( with box size=0.00010 ) ==> all the open and close prices end by "1" !!!
If you have studies using close prices then there appearence change !

REQUEST:
It would be interesting to define a parameter "reference price" or a "base price" for Renko chart that allow you to define the last digit.
For example if you want a 0 (zero) for the last digit, you define the "reference price" to 0.00000 or 1.00000. With a 0.00010 box size, all open and close price will be ALWAYS a multiple of the box size ( 1.00010, 1.00020, ..., 1.30170, 1.30180, ... )
Same thing if you want "5" as the last digit. You define "reference price= 0.00005 or 1.00005 ( with a box size greater than 0.00010 )

Steps to reproduce this issue

when you change the beginning date of the chart ( with a box size greater than 0.00010 and a 5 digits symbol), the last digit of open and close are different

Comments (0)
History
Issue basics
  • Type of issue
    Feature request
  • Category
    Stability
  • Targeted for
    MultiCharts Future Releases
  • Status
    Confirmed
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 (4)
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates