It would be great if one could use the DRAWTEXT command also in strategies and not only in indicators.

Another function that I often are missing is the possibility to

• export all customized settings from Demo to live and vice versa; drawings, chart, indicators, proorders, proscreeners..etc.,
• Alarms set in Proorder is pushed to mobile device

Cheers Kasper

Correction

”

• Alarms set in Proorder is pushed to mobile device”

I actually meant

• Alarms set in ProRealTime is pushed to mobile device

I suggest that the TIMEFRAME keyword be matched by ENDTF (or ENDTIMEFRAME) keyword, just like IF …. ENDIF, to make sure that if someone forgets to use again TIMEFRAME to return to the original time frame, a warning is issued.

In the below example from PRT documentation, if the second TIMEFRAME is forgotten, the screener will yield erratic results. Warning about a missing matching ENDTF might help realize there is some unwanted logic error:

REM Condition 1 and 2: MACD weekly < 0 and increasing
TIMEFRAME(weekly)
MyMACD = MACD[12,26,9](Close)
c1 = MyMACD < 0 AND MyMACD > MyMACD[1]
REM Condition 2: Daily Stochastic < 30
TIMEFRAME(daily)
MySTO = Stochastic[14,3](Close)
c2 = MySTO < 30
REM Set Stop Level
MyStop = High[1]
REM Criteria: Proximity to the high of the previous day
Criteria = (Close / MyStop - 1) * 100
REM Condition 3: Price is less than previous day's high or no more than 5% above it.
c3 = Criteria < 5
SCREENER[c1 AND c2 AND c3](Criteria)

Optimizer – to show ALL the results, not just the top x results. Option to select how many results to view on one page – ie show me top 10, top 100 results.

Optimizer – to iterate through timeframes (temporal and non temporal) as well as through variables. Select in advance what timeframes to include.

Optimizer – ability to shift variables up and down in priority order

Optimizer – ability to iterate up and DOWN

Optimizer – option to change default sort to hit rate for example

Optimizer – to navigate more inteligently through iterations rather than a “brute force” / “dumb” style. Options to select iteration algorithm. There are many different algorithms you can use. For example to follow the profit trail –  a “ripple” algorithm: If you had 4 variables to iterate through, select the mid point or starting point for 2, 3, 4 and iterate through 1. Select the most profitable point of variable (or best hit rate – option to select) 1. From there iterate through 2. Select the most profitable point of 1 and 2. Iterate through 3… and so on. After this is done, do it again, and again, and again. until the result can’t get better. Much faster and no need to try every single combination.

I wrote this before but i have to say so again. THis 12h limit is MEGA ANNOYING! Everyday i lose data because of this stupid logging out.

Can  they PLEASE create a possibility to save ongoing tests and resume them after logging out (if that has to be done)!?

Yes, losing code is of course worst but also that it is impossible to resume backtests that were running before one logs out is more than annoying.

That should be changed,  along with an option to archive and save backtest results.