MULTICHARTS 8.0 BETA 1– WHAT’S NEW

Download MultiCharts 8.0 Beta

MultiCharts 8.0 Beta 1 is big step forward for our traders. It’s the first time that EasyLanguage scripts can be used on 64-bit software, which means only your physical memory is the limit for backtesting, charting, optimization or trading. Several smaller features were added, and bugs affecting stability and data handling were addressed.

Follow us on Twitter, Facebook, LinkedIn, and Traders’ Blog to get timely updates about important changes. Share opinions on the MultiCharts Discussion Forum – http://www.multicharts.com/discussion.

Report bugs and request features in our Project Management system – http://www.multicharts.com/pm/.

NEW FEATURES

64-bit version

64-bit means that all modules in MultiCharts were rewritten to be 64-bit, so they can use all available RAM on a computer. Performance of the application is now limited only by the amount of physical memory in your computer. Limitation on number of bars on charts, mapping and importing ASCII files more than 4GB, number of symbols and plots in Scanner, and displaying strategy performance report with large number of trades were all lifted in the 64-bit version. More information here – http://www.multicharts.com/pm/viewissue.php?issue_no=MC-325, and here http://www.multicharts.com/pm/viewissue.php?issue_no=MC-131, and here –http://www.multicharts.com/discussion/viewtopic.php?t=6534.

Getting Started Wizard

Now the first time you launch MultiCharts you will see a wizard that helps you configure your data feed and create chart.

IWBank data feed and broker added

IWBank is one of the top Italian brokers that offers attractive rates and a premier connectivity to Italian and world markets.

Gather information from a bar through mouse-click

Information gathered about a bar through a mouse click. More info here –http://www.multicharts.com/pm/viewissue.php?issue_no=MC-394. There are new keywords that allow processing of captured information in scripts; check our Wiki in the near future for complete details.

aiCalcReason

aiCalcReason – specifies return of the calculation reason. GetAppInfo will return the value, indicating the reason of calculation initialization.

Notes:

calcreason_default – calculation is to be initialized when the new bar/tick appeared.

calcreason_mouseLClick – calculation is to be initialized after left-click on the chart.

calcreason_mouseRClick – calculation is to be initialized after right-click on the chart.

calcreason_timer – the calculation is to be initialized after expiration of RecalcLastBarAfter timeout.

ProcessMouseEvents

Declares that the study processes mouse events.

Usage

[ProcessMouseEvents = LogicalValue]

Where: LogicalValue – a true/false value; True = Enable; False = Disable

Notes:

  • If this attribute is not present in the study’s code, the indicator based in the mouse events will not be calculated.
  • Can be used only in signals and indicators

Example:

[ProcessMouseEvents = True];

MouseClickBarNumber

After a mouse click on the bar, returns the numerical value indicating the bar number from the beginning of the data series

Usage:

MouseClickBarNumber

Example:

MouseClickBarNumber will return 250 after a mouse click on the 250th bar on the chart from the beginning of the data series.

MouseClickCtrlPressed

Returns True if the Ctrl button is pressed on the keyboard simultaneously with a mouse click.

Usage:

MouseClickCtrlPressed

MouseClickShiftPressed

Returns True if the Shift button is pressed on the keyboard simultaneously with a mouse click Usage:

MouseClickShiftPressed

MouseClickDataNumber

Returns the numerical value indicating the data series number after a mouse click on the data series

Usage:

MouseClickDataNumber

Example:

MouseClickDataNumber will return 1 after left-click on the main chart with the main data series.

MouseClickDataNumber  will return 2 after left-click on the sub-chart with the second data series.

MouseClickDateTime

Returns a double-precision decimal value in Julian (OLE) date-time format indicating the closing date of the bar after a click on the bar.

Usage:

MouseClickDateTime;

Example:

MouseClickDateTime will return a value of 39449.65625000 for 3:45 PM

MouseClickPrice

Returns a numerical value indicating price level of the mouse pointer position after a click on the chart.

Usage:

MouseClickPrice;

Example:

MouseClickPrice will return 139.60 after a click on the chart on the 139.60 price level.

GetPositionOpenPL keyword updated

Returns Open PL value in:

  • Symbol currency for Dukascopy (calculated on MultiCharts side)
  • Account currency for FXCM (calculated on the broker’s side)
  • Symbol currency for Interactive Brokers (calculated on MultiCharts side)
  • Symbol currency for LMAX (calculated on the broker’s side)
  • Symbol currency for MB Trading (calculated on MultiCharts side)
  • Symbol currency for Open E Cry (calculated on the broker’s side)
  • Symbol currency for Patsystem (calculated on the broker’s side)
  • Account currency for PFGBEST (calculated on the broker’s side)
  • Symbol currency for Trading Technologies (calculated on MultiCharts side)
  • Symbol currency for Zen-Fire (Rithmic) (calculated on the broker’s side)

Usage:

GetPositionOpenPL(Symbol, Account)

Where: Symbol – the name of the instrument.
Account – account number at broker.

Example:

Will return 15 if the current value in “Open PL” column in “Order and Position Tracker” window for the account is 15 dollars.

New keyword “GetUserName”

It returns info from ‘registration name’ field, i.e. the MultiCharts license. This allows third-party developers to authorize studies to particular MC licenses and not only to UserIDs (which may change as hardware changes). More info here –http://www.multicharts.com/pm/viewissue.php?issue_no=MC-796. Check our Wiki for complete details – http://www.multicharts.com/trading-software/index.php/GetUserName

RecalсPersist keyword added

Used in variable declaration statements, before a variable name, to specify that the value of the variable is to be updated on every tick and the latest value of this variable is to be saved after the study recalculation.

Usage:

Declaration:[RecalcPersist]Name(InitialValue1)

Notes:

  • This keyword can be used only with variables.
  • The variable with such an attribute cannot be serial type.

Example:

Declare Max as a numerical value, updated on every tick, with initial value of 100. After study recalculation, the latest value of Max will be saved:

Variable:[RecalcPersist] Max(100);

#return

Returns the control from the study script by analogy with the corresponding C++ statement. Does not return any value.

Usage:

#return;

Notes:

Can be used in all types of studies.

Adding/Removing columns in Optimization Report

You can now add/remove columns in the Optimization Report. More info here –http://www.multicharts.com/pm/viewissue.php?issue_no=MC-172.

Access to any bar from a script – new keywords

Now you can access any bar of a price series from a PowerLanguage script with new keywords that are listed below.

symbol_open
symbol_high
symbol_low
symbol_close
symbol_volume
symbol_openint
symbol_date
symbol_time
symbol_ticks
symbol_upticks
symbol_downticks
symbol_time_s

These words return the same thing as corresponsind words without the “symbol_” prefix, but

1)    Bars back are not limited by MaxBarsBack, and are limited only by the beginning of the data series

2)    Bars forward are not limited by zero, and are only limited by the end of the data series

So, you can address any bar irrelevant of which bar you are currently calculating on. Complete information will be posted in our Wiki soon.

Other features

  • Connection status messages added to Logs tab in Order and Position Tracker for PFG broker.
  • Multiple exchange gateways support was added for Trading Technologies profile to accommodate implementation of Advantage Futures.
  • Clients can now connect to Demo and Live accounts from PFG at the same time, even if both use same ports.
  • Logging for order modifications is now enabled in Logs tab in Order and Position Tracker, since TT broker converts every market order to limit, and every stop order to stop-limit.
  • Open P/L and AvgEntryPrice are now calculated based on prices known to broker profile, and AvgSellPrice is taken from API.
  • Strategy name is now displayed in status line. More info here –http://www.multicharts.com/pm/viewissue.php?issue_no=MC-80.
  • Extended hours are now used for eSignal data feed to get volume outside regular trading hours.
  • Unicode support in Symbol Dictionary. More info here – http://www.multicharts.com/pm/viewissue.php?issue_no=MC-370.
  • Symbol Mapping improved; it’s now more intuitive after choosing Broker symbol in the Lookup window.
  • Price scale markers are now always displayed according to user specifications if such exist.
  • Holiday List updated for 2012.

BUGS FIXED

Charting/Data Handling

  • Magnification to one minute in the Bar Magnifier didn’t work on daily charts built out of minute data.
  • Ask/Bid values form a previously connected profile would appear on the Trade Panel for a new broker profile (eg values from ZenFire would appear on a PFG profile).
  • Prices were significantly different for some PFG symbols on historical data and in real-time. More info here –http://www.multicharts.com/discussion/viewtopic.php?f=1&t=9855.
  • Ask and Bid for EURUSD.FXCM symbol from IQFeed would have volume equal to zero.
  • Problems displaying fractional prices for PFG symbols with fractional price scales.
  • Spikes in data from Interactive Brokers when new high or low values arrive.
  • Interactive Brokers shows incorrect volume in real-time data.
  • Holes in data when requesting minute chart data from TradeStation.

Trading

  • Signal without IntrabarOrdergeneration (IOG) would produce more than one order per bar if another signal with IOG was applied to the chart.

Scripts/Calculations

Stability/Performance

  • Exception when trying to add an ASCII Mapping symbol from within MultiCharts.
  • Assert when doing partial exit of a position in Synchronous Autotrading mode, and no dialog window for closing the position.
  • Memory leak when autotrading with ZenFire Local Sim broker.
  • SSL connection for some PFG users gave an error.
  • Stack Overflow exception after opening Master Strategy after opening several other windows.
  • Connection would constantly break with PFG API.
  • Some QMD data archives would not import due to being corrupted.
  • Exception in FIXServer when working with PFG charts and DOM.

Usability/Visual

  • Problems with display of drawings on charts.
  • Added proper message when user tries to open too many workspaces at once.
  • Visual Order dialog window would not scroll.
This entry was posted in Beta on .

2 thoughts on “MULTICHARTS 8.0 BETA 1– WHAT’S NEW

  1. Pingback: MultiCharts 8 64-bit - MultiCharts

Comments are closed.