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

Plotting cumulative delta as indicator, for renko price bar users

action_vote_minus_faded.png
2
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, cumulative delta can only be used as a chart type, which means that users of renko price bars are not able to track pivots between price and delta.
If cumulative delta could be used as an indicator, then it would be possible to have the CD study print a new bar whenever the renko price prints a new bar. This is invaluable to cumulative delta traders who use renko price bars.

Steps to reproduce this issue

If you plot a renko price chart of an instrument, and add a cumulative delta price chart of the same instrument, you will need to choose settings for each chart independently. Because cumulative delta is treated as a chart type only and not an indicator, it is impossible to compare high and low pivots between price and delta when using renko price bars.

Comments (1)
#0
user-offline.png  JoeTrader (Guest)
Mar 03, 2016 - 12:27

I tried to build Net Volume (Volume traded at Ask - Volume traded at Bid; or Volume traded Uptick - Volume traded Dntick) for Renko chart to no avail.
Same method works for Range bar charts though.

History
Issue basics
  • Type of issue
    Feature request
  • Category
    Usability
  • Targeted for
    Not determined
  • Status
    Under Review
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
    Critical
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