+1 888 340 6572
MultiCharts Project Management

MultiCharts Project Management Timeline

December 11, 2017
feature_request_tiny.png 07:45  Feature request MC-1655 - Optimization API in Multicharts please !
Alex MultiCharts (Alex MultiCharts) : Target milestone changed: MultiCharts 12 ⇒ MultiCharts Future Releases
December 06, 2017
feature_request_tiny.png 11:36  Feature request MC-2382 - Saving data portfolio trader after shutdown
buffetuoren (buffetuoren) : Issue created
Good day! I would like to see in the package of improvements the following functionality: portfolio trader today does not save any data of trading after the shutdown, however, it would be very proper to have the ability to save accumulated data from auto trading even turning off the portfolio of the trader. To the stored parameters
feature_request_tiny.png 09:49  Feature request MC-2017 - expose optimization functionality @ API level
Alex MultiCharts (Alex MultiCharts) : Target milestone changed: MultiCharts 12 ⇒ MultiCharts Future Releases
November 30, 2017
feature_request_tiny.png 22:43  Feature request MC-2337 - TradingView Integration, Simplified Detail Analysis Tools and More Intuitive Overall Platform
FidelisCapital (Fidelis) : Description updated
feature_request_tiny.png 20:19  Feature request MC-2381 - Chart Printing all lines black.
bowlesj3 (bowlesj3bt) : Issue created
For those of us who don't use colour cartridges in our printers since we never need them it would be nice if there was a feature to have all chart printing lines printed in black. This would include price bars, bollinger bands, RSI, %R, moving averages, etc. Unfortunately my printer's gray scale setup setting does not seem to work for all colours that MultiCharts uses and this renders the chart printing useless for me.
November 29, 2017
feature_request_tiny.png 15:19  Feature request MC-2337 - TradingView Integration, Simplified Detail Analysis Tools and More Intuitive Overall Platform
FidelisCapital (Fidelis) : Description updated
feature_request_tiny.png 13:06  Feature request MC-2380 - User-defined/created themes for scanners and order and position tracker windows
Retest (Retest) : Issue created
I find the available themes aren't very friendly to the eye--either there's too much contrast or not enough. Why not give the user the ability to control the style properties like you've done with the charts? Thanks.
November 27, 2017
feature_request_tiny.png 09:10  Feature request MC-2379 - Bitfinex Exchange of Bitcoin
bomberone1 (bomberone1) : Issue created
Please add the connection to Bitfinex.

https://www.bitfinex.com/

Bitfinex is the world's largest and most advanced bitcoin exchange that offers the most liquid order book in the world with all type of order like regolar exchange and professional API to connect all 3ed trading platform already created for trading futures,stocks,forex,etc.. in regulated markets (CME;EUREX,LME,etc...) with minimal slippage.

PRO

1. IT's designed like regulated markets (CME;EUREX,LME,..) to have the same experience to trade in regulated markets.

2.Bitfinex allows for users to trade with up to 3.3x leverage.

3.The margin funding market provides a way to earn interest on Euro, US Dollar, Bitcoin, Bcash, Ethereum, Iota, Litecoin, EOS, NEO, Dash, Zcash, Ethereum Classic, Monero, Sentiment, Ripple, OmiseGO, ETP, and Eidoo.

4.Order Types
Limit, Market, Stop, Trailing Stop, Fill or Kill, Iceberg Orders, One Cancels Other (OCO), Post Only, Hidden Order, TWAP

5. API
Bitfinex's API is designed to offer an easy and efficient way to build digital asset trading applications and tools: create your own charts, monitor and edit your orders and positions, track your trading history and wallets movements. Discover all the possibilities.

https://docs.bitfinex.com/docs
https://docs.bitfinex.com/docs/open-source-libraries
https://docs.bitfinex.com/docs/api-access

November 26, 2017
bug_report_tiny.png 13:36  Bug report MC-2378 - Backtest and live trading is not consistent
Ettienne (et1hugo) : Description updated
bug_report_tiny.png 10:30  Bug report MC-2378 - Backtest and live trading is not consistent
Ettienne (et1hugo) : Description updated
bug_report_tiny.png 10:09  Bug report MC-2378 - Backtest and live trading is not consistent
Ettienne (et1hugo) : Description updated
bug_report_tiny.png 05:29  Bug report MC-2378 - Backtest and live trading is not consistent
Ettienne (et1hugo) : Description updated
bug_report_tiny.png 05:13  Bug report MC-2378 - Backtest and live trading is not consistent
Ettienne (et1hugo) : Description updated
bug_report_tiny.png 05:03  Bug report MC-2378 - Backtest and live trading is not consistent
Ettienne (et1hugo) : Issue created
Hi guys

There seems to be a difference between automated trading and the back test engine in terms of the messages passed to the strategy regarding orders being filled/cancelled/rejected. The Environment.CalcReason seems to always reflect Default in back testing with all the options checked in the Strategy Properties under "Recalculate on Broker Events". Additionally, none of the "OnBroker****" methods are fired either. While the manual does point out this distinction on p. 65 it not quite clear why that is the case and why the developer should be burdened with two different execution paths in a strategy to handle this discrepancy, one for back testing and another for live trading.

The back test engine should simulate the broker as best possible and as such should raise these events irrespective of whether the strategy is running in a back test or live. I believe this is also an issue with the TradeManager API and OCO orders looking at other issues logged. It would be good to smooth out these issues in order to bring the back test more in line with what would happen in a live trading scenario. This obviously also applies for the portfolio back testing. Thank you in advance for feedback.

Kind regards
Ettienne
November 20, 2017
feature_request_tiny.png 08:59  Feature request MC-2377 - Allow Position Execution and Order Generation to use Chart Data vs Broker Data
Scott (ascottwalls) : Issue created
Currently
November 16, 2017
feature_request_tiny.png 09:46  Feature request MC-2337 - TradingView Integration, Simplified Detail Analysis Tools and More Intuitive Overall Platform
FidelisCapital (Fidelis) : Description updated
November 15, 2017
feature_request_tiny.png 11:23  Feature request MC-2337 - TradingView Integration, Simplified Detail Analysis Tools and More Intuitive Overall Platform
FidelisCapital (Fidelis) : Description updated
feature_request_tiny.png 07:28  Feature request MC-2337 - TradingView Integration, Simplified Detail Analysis Tools and More Intuitive Overall Platform
FidelisCapital (Fidelis) : Title updated
November 14, 2017
bug_report_tiny.png 09:16  Bug report MC-2373 - Multicharts.NET latest: using System.Windows.Forms.DataVisualization.Charting; fails in PowerLanguage Editor but compilation succeeds in Visual Studio
Alex MultiCharts (Alex MultiCharts) : Status changed: Under Review ⇒ Not a bug
November 13, 2017
feature_request_tiny.png 13:55  Feature request MC-2337 - TradingView Integration, Simplified Detail Analysis Tools and More Intuitive Overall Platform
FidelisCapital (Fidelis) : Description updated
feature_request_tiny.png 13:53  Feature request MC-2337 - TradingView Integration, Simplified Detail Analysis Tools and More Intuitive Overall Platform
FidelisCapital (Fidelis) : Description updated
feature_request_tiny.png 13:53  Feature request MC-2337 - TradingView Integration, Simplified Detail Analysis Tools and More Intuitive Overall Platform
FidelisCapital (Fidelis) : Title updated
feature_request_tiny.png 12:25  Feature request MC-2337 - TradingView Integration, Simplified Detail Analysis Tools and More Intuitive Overall Platform
FidelisCapital (Fidelis) : Description updated
feature_request_tiny.png 12:18  Feature request MC-2337 - TradingView Integration, Simplified Detail Analysis Tools and More Intuitive Overall Platform
FidelisCapital (Fidelis) : Title updated
November 10, 2017
bug_report_tiny.png 15:10  Bug report MC-2376 - xxx Bars Back Setting for Data Range loads appr. 3 months of data only
Alex MultiCharts (Alex MultiCharts) : Status changed: Under Review ⇒ Not a bug
bug_report_tiny.png 14:56  Bug report MC-2369 - Errors in position handling on OandA account
Alex MultiCharts (Alex MultiCharts) : Status changed: Under Review ⇒ Need Details
bug_report_tiny.png 14:52  Bug report MC-2375 - Portfolio Trader with 2 oposing strategies running on same instrument with same timeframe & history, on same broker: PNL graph looks surprisingly incorrect: instead of one line, there are two taking totally different paths
Alex MultiCharts (Alex MultiCharts) : Status changed: Under Review ⇒ Not a bug
bug_report_tiny.png 07:16  Bug report MC-2362 - Portfolio Backtester: for multiple strategies set on different symbols, backtester loops number = product of all params across all strategies = Grossly unexpected and missleading! This is a fault, not a lack of optimization. Strategy param sets should be
Alex MultiCharts (Alex MultiCharts) : Status changed: Under Review ⇒ Not a bug
November 08, 2017
bug_report_tiny.png 15:21  Bug report MC-2352 - Money Management Settings in Portfolio Trader do not work when # shares or dollars are specified within a strategy
Alex MultiCharts (Alex MultiCharts) : Status changed: Under Review ⇒ Not a bug
feature_request_tiny.png 15:04  Feature request MC-231 - Automated trading via Strategies Panel
Alex MultiCharts (Alex MultiCharts) : Target milestone changed: Not determined ⇒ MultiCharts 9.0 (RELEASED)
feature_request_tiny.png 15:04  Feature request MC-231 - Automated trading via Strategies Panel
Alex MultiCharts (Alex MultiCharts) : Status changed: Under Review ⇒ Released
bug_report_tiny.png 07:34  Bug report MC-2374 - not an issue. simple to type-over in blue. everyone else probably knows that already! :-)
waves (waves) : Description updated
bug_report_tiny.png 07:33  Bug report MC-2374 - not an issue. simple to type-over in blue. everyone else probably knows that already! :-)
waves (waves) : Description updated
bug_report_tiny.png 07:29  Bug report MC-2374 - not an issue. simple to type-over in blue. everyone else probably knows that already! :-)
waves (waves) : Title updated
November 07, 2017
bug_report_tiny.png 10:44  Bug report MC-2376 - xxx Bars Back Setting for Data Range loads appr. 3 months of data only
Zheka (Zheka) : Issue created
When selecting xxx Bars Back option in Instrument settings for a chart or in PT, MC loads only appr. 3 months of data.
November 03, 2017
bug_report_tiny.png 17:30  Bug report MC-2375 - Portfolio Trader with 2 oposing strategies running on same instrument with same timeframe & history, on same broker: PNL graph looks surprisingly incorrect: instead of one line, there are two taking totally different paths
andb (andrei.reiand@gmail.com) : Issue created


When applying two opposite signals in their own separate Strategies but on same symbol within a portfolio trader session, one would expect that when a backtest is run, the two completely oposing PNL Shapes would cancel eachother and result in a completely FLAT Aggregated PNL Line ... well, that's not the case: Aggregated PNL Line has actually two separated High & Low (green & red) lines ... which make little sense ... there should be a flat zero line.
bug_report_tiny.png 14:04  Bug report MC-2374 - not an issue. simple to type-over in blue. everyone else probably knows that already! :-)
waves (waves) : Issue created
format window > back space to clear pixels value with intent of entering new value. MC locks up. easy to simply type-over in blue. everyone else probably knows that already. nevertheless, the penalty for unnecessary backspacing seems too severe! :-)
November 02, 2017
bug_report_tiny.png 16:59  Bug report MC-2373 - Multicharts.NET latest: using System.Windows.Forms.DataVisualization.Charting; fails in PowerLanguage Editor but compilation succeeds in Visual Studio
andb (andrei.reiand@gmail.com) : Issue created
I was surprised to see a situation (as in the attached) where I can Build successfully the solution in VStudio but it errors out in PowerLanguage.NET Editor ... this is a bit strange, usually the two are consistent in the errors they output.
October 31, 2017
feature_request_tiny.png 20:08  Feature request MC-2372 - Customizable MaxBarsBack for Data1, Data2,... to facilitate integration of Weekly Indicators such as COT in data2,... with Daily Data1
JoeTrader (gboulay) : Description updated
October 30, 2017
feature_request_tiny.png 19:00  Feature request MC-2372 - Customizable MaxBarsBack for Data1, Data2,... to facilitate integration of Weekly Indicators such as COT in data2,... with Daily Data1
JoeTrader (gboulay) : Issue created
Hi,

I currently use IQFeed to get data and they provide data for the Commitment of Traders (COT) from September 2007 forward which segments you can insert as instruments in data2, data3 and so forth. It is a weekly data. I also use a strategy (signal) based on daily bars with a 500 maxbarsback requirement to compute correctly. However, I am not able to insert a weekly indicator such as the COT in the signal because the computation of the indicator, either embedded or through a function, in the script of the signal creates a maxbarsback of 500 WEEKS which renders the strategy by itself and the indicator unusable, even without coding the COT indicator as a condition, but just by triggering the computation of this weekly indicator in the signal.

I was told to use or create a globalvariable dll to compute the indicator outside of the signal, but this is not supported by Multicharts, is not in easylanguage and would not work with MC Portfolio Trader, such that this is not a useful fix for the situation. From what I heard, Tradestation supplies easy access to the COT and allows easy integration within a strategy.

So, a fix for this would be appreciated, maybe simply but allowing the maxbarsback setup to be customized based on the various data1, data2 and so forth required for the signal. In order to work, I need 500 data1 bars and only some 15 weekly data2, data3,... bars.

Thank you for your consideration of this feature request.

I tried the fix suggested below in comments(1) and it doesn't resolve the issues described above with the signal.

August 10, 2017
icon_build.png 12:00 11.0
New version released
icon_build.png 00:00 11.0
New version released
icon_build.png 00:00 11.0
New version released