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

Referencing Volume Profile using easylanguage

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

I think it would be of great help to traders if they could reference prior vpocs and value areas for both indicator construction and possibly strategy automation. I know this is possible using MC.net but was wondering when this would be possible using regular MC and easylanguage.

Steps to reproduce this issue

Try to reference VPOC's using easylanguage.

Comments (3)
#1
user-offline.png  bomberone1 (bomberone1)
Dec 05, 2016 - 07:47

It would be nice, if we get sooner the possibility to use function of volume profile and not waite mc.11

#2
user-offline.png  rramse (rrams)
Dec 06, 2016 - 13:38

At least provide the formula used to calculate the value area and point of control for the built-in volume profile indicator. so we can try to match those numbers with a signal.

#3
user-offline.png  hdtrade (htrader)
Jul 27, 2017 - 14:38

To be blunt this particular issue drives me crazy. It seems that I should be able to easily reference the volume profile info that multicharts already generates and plots on the chart for indicators and strategies in powerlanguage. For example I want to plot yeterdays VAL, VAH and POC on todays session. I doubt you guys will ever fix this oversight in the profile settings and it wouldn't be a problem if I could reference the profile values in powerlanguage. I want to write some strategies that reference those levels but without have to become a computer programmer and use .net. I currently use other platforms to fulfill my volume profile needs in conjunction with multicharts.

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