+1 888 340 6572
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-1248

MultiCharts.NET PowerLanguage documentation and code commenting improvements

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


Apologies if there is already a feature request for this, but I couldn't find it.

I was having some real issues trying to find where the PowerLanguage .NET library documentation and tutorials were, but after spending a while looking through the wiki site and forums, it became apparent that there it is lacking! I'm very surprised that such a polished product has so little documentation for the API/programming library.

The bundled PowerLanguage CHM is nowhere near what I would call documentation and it doesn't even include a complete list of parameters for the PowerLanguage.Functions. The only way to see what properties are available is to use the intellisense!

e.g. PowerLanguage.BollingerBand - there is no way to see that there is a property called "numdevs" without using intellisense.

Please consider expanding the CHM or creating a webpage to provide comprehensive coverage of everything available. Not just the names of functions and properties, but descriptions of what they are, as well as links to examples etc.

e.g. http://www.ninjatrader.com/support/helpGuides/nt7/index.html?bollinger_bands.htm

Please consider providing more "How To" videos, written tutorials and user guides fo signal and indicator development. Especially a "How to get started" tutorial explaining the basics of creating a strategy.

I know there are plenty of indicators and signals included with the install which provide starting points, but there is not one single code comment explaining what is going on in these files. What is more, the variable names are poorly chosen and hard to read. I'm an experienced C# developer so I can understand what is going on, but it must be very difficult for someone new to the language and this doesn't need to be the case.

The following posts from other users back up what I am saying:





Steps to reproduce this issue

Feature request - documentation and code commenting improvements

Comments (3)
user-offline.png  Black Wood (Id2)
Nov 02, 2015 - 04:44

Hi Multicharts.
Right now is November 2015, but still there is no API documentation
for MC.Net.
Why is so difficult to make them. Use at least DOCU from C# resume examples or
copy what NinjaTrade is doing.
To step into trading with MC.NET is a way to steep even for experience 

user-offline.png  MultiCharts Support (MultiCharts)
Nov 21, 2015 - 01:41

In case you have any questions regarding C# coding we recommend referencing MSDN for information. Interfaces and classes available in MultiCharts .Net are described in MC .Net help file (PowerLanguage .Net Editor->Help tab-> PowerLanguage .Net Help). You can also find the code examples in the source code of the prebuilt MultiCharts studies (PowerLanguage .Net Editor->File tab->Open).
MultiCharts .NET Programming guide that contains important and useful information not only for beginners but for experienced MC .Net users as well. This is the recommended "Getting started for programming in MultiCharts .Net": http://www.multicharts.com/downloads/MultiCharts.NET-ProgrammingGuide-v1.0.pdf 
Wiki format: http://www.multicharts.com/trading-software/index.php/Category:.NET_Programming_Giude


Additional information

Issue basics
  • Type of issue
    Feature request
  • Category
  • Targeted for
    MultiCharts 8.5 (RELEASED)
  • Status
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (2)
People involved
  • Posted by
    user-offline.png  EdL (EdL)
  • Owned by
    Not owned by anyone
  • Assigned to
    Not assigned to anyone
  • Subscribers
    1 subscriber(s)
    Click here to show the list of subscribers
Times and dates
  • Posted at
  • Last updated
Issue details
  • Resolution
    Not determined
  • Severity
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