MultiCharts Project Management Timeline

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.

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.

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.

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.

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....

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.

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.

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

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!!!!

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...

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.

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.