+1 888 340 6572
MultiCharts Project Management

MultiCharts Project Management Timeline

21 de septiembre de 2018
feature_request_tiny.png 11:52  Feature request MC-734 - Feature Request - a button on the toolbar and/or a shortcut key for "View/strategy performance report", for "Format Signal" and for "Format/Strategy Properties"
abood (aboodi_123) : '7' is now unconfirmed for this issue
feature_request_tiny.png 11:52  Feature request MC-734 - Feature Request - a button on the toolbar and/or a shortcut key for "View/strategy performance report", for "Format Signal" and for "Format/Strategy Properties"
abood (aboodi_123) : '7' is now confirmed for this issue
feature_request_tiny.png 11:52  Feature request MC-734 - Feature Request - a button on the toolbar and/or a shortcut key for "View/strategy performance report", for "Format Signal" and for "Format/Strategy Properties"
abood (aboodi_123) : '8.0' is now unconfirmed for this issue
feature_request_tiny.png 11:52  Feature request MC-734 - Feature Request - a button on the toolbar and/or a shortcut key for "View/strategy performance report", for "Format Signal" and for "Format/Strategy Properties"
abood (aboodi_123) : '8.0' is now confirmed for this issue
19 de septiembre de 2018
bug_report_tiny.png 20:41  Bug report MC-2500 - Pyramiding is not working when running live (ok on backtest)
Alex MultiCharts (Alex MultiCharts) : Status changed: Under Review ⇒ Not a bug
bug_report_tiny.png 18:01  Bug report MC-2499 - PT: wrong trade size with Cash Per Trade setting
Alex MultiCharts (Alex MultiCharts) : Status changed: Under Review ⇒ Need Details
bug_report_tiny.png 17:58  Bug report MC-2504 - Compiler issue
Alex MultiCharts (Alex MultiCharts) : Status changed: Under Review ⇒ Confirmed
bug_report_tiny.png 17:58  Bug report MC-2504 - Compiler issue
Alex MultiCharts (Alex MultiCharts) : Target milestone changed: Not determined ⇒ MultiCharts 13
bug_report_tiny.png 17:50  Bug report MC-2501 - MC12 Optimize order flow has a new major bug that blocks exit stop order submission on bar of entry.
Alex MultiCharts (Alex MultiCharts) : Target milestone changed: Not determined ⇒ MultiCharts 12 (RELEASED)
bug_report_tiny.png 17:50  Bug report MC-2501 - MC12 Optimize order flow has a new major bug that blocks exit stop order submission on bar of entry.
Alex MultiCharts (Alex MultiCharts) : Status changed: Under Review ⇒ Released
bug_report_tiny.png 17:49  Bug report MC-2500 - Pyramiding is not working when running live (ok on backtest)
Alex MultiCharts (Alex MultiCharts) : Target milestone changed: MultiCharts 12 (RELEASED) ⇒ Not determined
bug_report_tiny.png 17:49  Bug report MC-2500 - Pyramiding is not working when running live (ok on backtest)
Alex MultiCharts (Alex MultiCharts) : Status changed: Released ⇒ Under Review
bug_report_tiny.png 17:48  Bug report MC-2500 - Pyramiding is not working when running live (ok on backtest)
Alex MultiCharts (Alex MultiCharts) : Status changed: Under Review ⇒ Released
bug_report_tiny.png 17:48  Bug report MC-2500 - Pyramiding is not working when running live (ok on backtest)
Alex MultiCharts (Alex MultiCharts) : Target milestone changed: Not determined ⇒ MultiCharts 12 (RELEASED)
feature_request_tiny.png 17:39  Feature request MC-1809 - Ctrl+R functionality
Alex MultiCharts (Alex MultiCharts) : Status changed: Under Review ⇒ Released
feature_request_tiny.png 17:39  Feature request MC-1809 - Ctrl+R functionality
Alex MultiCharts (Alex MultiCharts) : Target milestone changed: Not determined ⇒ MultiCharts 12 (RELEASED)
14 de septiembre de 2018
feature_request_tiny.png 22:41  Feature request MC-2508 - Renko Bar Chart Upgrades
TrendFirst (trendfirst1) : Issue created
I have a couple of requests regarding Renko Bar Charts.

The first is simple - please provide a time/tick countdown for Renko bars. I realize in the historical bars there is no time/tick aspect - they are based on points. But in the current Renko bar, there is a time/tick aspect, before it "rolls", if you will, to the Renko format. Please provide a time/tick countdown for the current Renko bar. Thanks.

The second is likely more complex. Please provide more accurate backtests when using Renko bars. As you likely know, backtests using Renko bars can be wildly optimistic. This request is related to number 1 above - if the current bar is an expanded range bar, it will not transition into a single Renko bar - it could be 2, 3, 4, 5 or more Renko bars. Say it's 4. The backtest will assume your entry is based on the first Renko bar in that series of 4 - but really your entry will happen at the 4th bar. If there was a way to adjust entries and exits for this effect, the backtests would be more accurate, and less optimistic. Thanks.

05 de septiembre de 2018
feature_request_tiny.png 23:49  Feature request MC-2507 - TradingView background dragging in Multicharts
hdtrader (hdtrader) : Issue created
The way TradingView does background dragging is way more user friendly. Having to select and unselect the background dragging button in multicharts is very tedious compared to the way TradingView does it, i.e. no button just click and move your mouse when you want to drag the background.
feature_request_tiny.png 23:38  Feature request MC-2506 - TradingView Pine Script Fill function in powerlanguage
hdtrader (hdtrader) : Issue created
I really like the 'fill' function in pine script to color and shade areas in tradingview. There is no way to do anything similar in powerlanguage, something like this has been needed for a long time.
feature_request_tiny.png 08:28  Feature request MC-2505 - Changing Flex Renko value from command line
AdrianP (AdrianP) : Issue created
Currently, we can quickly change our tick, contract and time charts from the command line by simply typing in whatever timeframe/compression we want, such as '100 tick' or '30 min' etc
.
I would like to propose this ability is added for FLEX RENKO as well.

Flex Renko requires 3 values. So, as an example we would type in "30 15 15 Renko" to plot. This will save us heaps of time from having to do multiple clicks every time.
03 de septiembre de 2018
bug_report_tiny.png 20:25  Bug report MC-2504 - Compiler issue
scooper (scooper) : Issue created
print("Start Time=",time:0:0," CC=",currentcontracts:0:0, Time of Data1 of Data5);

the above line of code compiles but the Time of Data1 of Data5 is not valid.....

you can also pass Time of Data1 of Data5 into functions as well and that compiles as well....
31 de agosto de 2018
feature_request_tiny.png 21:00  Feature request MC-2503 - Allow an option to send multiple orders per bar
scooper (scooper) : Issue created
Tradestation and other well known trading platforms all multiple orders to be sent per bar per signal calculation.

At present multiple orders in the same direction are summed up and one summed order is sent (using the optimize order flow option) OR (not using optimize order flow) only the first issued order is sent and the other orders are not sent which is very confusing and is not consistent with the way Tradestation works (so converted strategies will no longer work if they use multiple orders per bar and you do not use optimize order flow).

Please allow an option to send multiple orders per bar without summing into one large order. This is very helpful where you want to hide total market order and break an order into multiple chunks that do not show one big sized order to the market.
bug_report_tiny.png 19:41  Bug report MC-2502 - Paper trader triggers stops incorrectly
Will (wilkinsw) : Issue created
Hi,

In both MC12 and 11 (the only version I've checked), papertrader will trigger a buy stop when the quoted ask = buy trigger price.

If you test it, you'll quickly see so. When trading live.... that event alone ("quoted ask = buy trigger price.") does not trigger a resting stop. Someone has to trade at the price or worse to trigger the stop.

Currently stops can be triggered with price ever trading at the stops trigger price.

Please change this as it seems very unnecessary to introduce such inaccuracy into testing.

Thanks.
bug_report_tiny.png 19:28  Bug report MC-2501 - MC12 Optimize order flow has a new major bug that blocks exit stop order submission on bar of entry.
Will (wilkinsw) : Issue created
MC12 Optimize order flow has a new major bug that blocks exit stop order submission on bar of entry.




https://www.multicharts.com/discussion/viewtopic.php?t=51602
feature_request_tiny.png 15:00  Feature request MC-385 - Feature request: optimize on resolution/time frame
Alex MultiCharts (Alex MultiCharts) : Target milestone changed: MultiCharts 13 ⇒ Not determined
29 de agosto de 2018
bug_report_tiny.png 16:41  Bug report MC-2489 - MC 12.0.166.42 Hides indicators in subcharts above the first subchart that contains an instrument
Alex MultiCharts (Alex MultiCharts) : Status changed: Under Review ⇒ Released
bug_report_tiny.png 16:41  Bug report MC-2489 - MC 12.0.166.42 Hides indicators in subcharts above the first subchart that contains an instrument
Alex MultiCharts (Alex MultiCharts) : Target milestone changed: Not determined ⇒ MultiCharts 12 (RELEASED)
bug_report_tiny.png 00:09  Bug report MC-2500 - Pyramiding is not working when running live (ok on backtest)
scooper (scooper) : Issue created
When pyramiding and executing multiple entry orders with strategy automation the orders are not placed correctly and current contracts within the strategy are incorrect.

However, the order and position tracking window show the correct position of contracts purchased through the orders placed. BUT this is not what shows on the chart and manual orders are placed automatically which further compounds the problem.

A full video with source code and strategy settings can be viewed from the dropbox video link I have made

https://www.dropbox.com/s/6l9tnax77ik3j0d/PYRAMID%20ISSUE.mp4?dl=0

this is a huge problem. Please help!!!!
28 de agosto de 2018
bug_report_tiny.png 23:39  Bug report MC-2494 - PortfolioTrader with PaperTrader accounts: although PositionClose Date is in the Past, position is Open in PerformanceReport and Sync with Broker Positions doesn't happen
Alex MultiCharts (Alex MultiCharts) : Status changed: Under Review ⇒ Need Details
bug_report_tiny.png 23:35  Bug report MC-2492 - .NET 11 PortfolioTrader with a FlipFlop strategy fails to execute on 1minute bars (regardless of the source)
Alex MultiCharts (Alex MultiCharts) : Bug report MC-2493 now depends on the solution of this Bug report
bug_report_tiny.png 23:35  Bug report MC-2493 - Portfolio Trader execution is totally unreliable (FlipFlop Strategy on 1min bars don't execute)
Alex MultiCharts (Alex MultiCharts) : This Bug report now depends on the solution of Bug report MC-2492
bug_report_tiny.png 23:34  Bug report MC-2492 - .NET 11 PortfolioTrader with a FlipFlop strategy fails to execute on 1minute bars (regardless of the source)
Alex MultiCharts (Alex MultiCharts) : Status changed: Under Review ⇒ Duplicated
bug_report_tiny.png 23:34  Bug report MC-2492 - .NET 11 PortfolioTrader with a FlipFlop strategy fails to execute on 1minute bars (regardless of the source)
Alex MultiCharts (Alex MultiCharts) : Issue closed
bug_report_tiny.png 23:33  Bug report MC-2493 - Portfolio Trader execution is totally unreliable (FlipFlop Strategy on 1min bars don't execute)
Alex MultiCharts (Alex MultiCharts) : Status changed: Under Review ⇒ Need Details
bug_report_tiny.png 23:21  Bug report MC-2495 - PortfolioTrader with PaperTrader - closing a portfolio (that was running live) without canceling positions and re-opening it again with option "use actual position at the broker" closed my broker positions entirely
Alex MultiCharts (Alex MultiCharts) : Status changed: Under Review ⇒ Need Details
27 de agosto de 2018
bug_report_tiny.png 16:31  Bug report MC-2499 - PT: wrong trade size with Cash Per Trade setting
Zheka (Zheka) : Issue created
See Reproduction steps below.

There might be an explanation (exchange rate at trade exit is applied for conversion?), but it is practically wrong and does not serve the purpose of accurate backtesting...
25 de agosto de 2018
feature_request_tiny.png 02:27  Feature request MC-2498 - easier time segment change for charts
wildmur (wildmur7) : Issue created
The current, fastest method of moving data series ahead/backwards in time is to use the .csy in the command prompt box at the bottom. This is cumbersome as it requires selecting each data series, one at a time, then selecting the command, and a person has to scroll back to select the next data series to move forward.
It would be very convenient to have a button that is easily customizable to move all data series and the entire chart forward for example 40 days. Then I can analyze results, hit the button, and the entire chart moves forward another 40 days. Another button could move it backwards 40 days. For example, I have a 40-day set of data and I move the entire set 40 days forward with the click of one button. Your updates are appreciated.
23 de agosto de 2018
bug_report_tiny.png 23:05  Bug report MC-2490 - Portfolio Trader - no continuity between sessions, no synchronization of itself with broker open positions
Alex MultiCharts (Alex MultiCharts) : Status changed: Under Review ⇒ Not a bug
bug_report_tiny.png 23:01  Bug report MC-2496 - Live running portfolio trader with @JY position open - @JY cannot be found under Open Positions in he Tracker Window
Alex MultiCharts (Alex MultiCharts) : Status changed: Under Review ⇒ Need Details
feature_request_tiny.png 13:44  Feature request MC-2497 - Improve RMC menus
AdrianP (AdrianP) : Issue created
I get the feeling that there aren't a lot of traditional chartists using Multicharts, drawing trendlines and such. As if there were, they would have noticed the cumbersome and inefficient use of the RMC menu structures, or lack thereof.

My request is to improve the menu structure when RMC on a particular item. Currently for example, if I draw a trendline, and wish to then extend it to the right, but not as a default, I first have to RMC, then select another menu option, then click another check box. Clearly this is a massive waste and can be improved 100%.

I would ask the MC developers to transfer many of the secondary menu choice items (after a RMC choice is made) to the 1st menu when first RMC.

The ultimate goal is to minimise the number of mouse clicks needed to achieve a task, while at the same time keeping things from getting out of hand with perhaps a menu choice that was too long. But this should not be an issue when we are dealing with the context sensitive nature of RMC. So in my example above, the choice to extend a trendline to the left or right would appear right when I RMC on the trendline. This will bring it into line with say Tradestation and Metastock, which have had this kind of menu structure for over a decade.

I hope this is clear. And when this logic is applied to many other secondary menu choices, I feel a substantial reduction of mouse clicks can easily be achieved.
08 de agosto de 2018
icon_build.png 16:00 12.0
New version released
icon_build.png 16:00 12.0
New version released
10 de agosto de 2017
icon_build.png 21:00 11.0
New version released
icon_build.png 09:00 11.0
New version released
icon_build.png 09:00 11.0
New version released
08 de agosto de 2017
icon_build.png 16:00 12.0
New version released
22 de noviembre de 2016
icon_build.png 16:00 10.0
New version released
icon_build.png 16:00 10.0
New version released
17 de noviembre de 2016
icon_build.png 16:00 10.0
New version released
07 de octubre de 2015
icon_build.png 08:00 9.1
New version released
icon_build.png 08:00 9.1
New version released
icon_build.png 08:00 9.1
New version released
06 de octubre de 2014
icon_build.png 08:00 9.0
New version released
icon_build.png 08:00 9.0
New version released
icon_build.png 08:00 9.0
New version released