Centralization of queries and suggestions on ProRealTime
- This topic has 363 replies, 84 voices, and was last updated 2 months ago by
.
-
#INCLUDE “filename” should be added to avoid cutting & pasting too many times. For example Nicolas’ TRAILING STOP code could be INCLUDED.
An option should allow to set the correct folder where INCLUDEed files should be uploaded from.
1 user thanked author for this post.
why not some kind of pop-up window after a new update ,whats is done/new
(for example)
walk forward optimazation added
problem with “x” fixed
..and so on.
2 users thanked author for this post.
A minor point but it’s now beginning to bug me….. Please is it possible for the Detailed report in backtesting to open up in a format that does not require extending the length of the window to see all results in the gross performance section ie auto fit for all information available. This also applies to the orders list and closed positions tabs – the columns (Entry, Exit, MAE, MFE) need to be automatically sized (widened) to fit the information. Currently I have to manually size everything each time I open up a new backtest report (PRT does not remember my sizing preferences) which gets very repetitive to say the least.
Also on that point, I would like to be able to choose which columns to show in the Orders and Closed positions tab as I have no use for the brokerage or value columns. Its needs a “wrench” icon like we have for other windows.
Thanks
A few suggetions:
- add UNDELETE for all objects/indicators on a chart;
- add a property to any object to allow/ban showing it in lower timeframes to supersede general option (which should remain for all objects); i.e. I want ALL objects to show in lower TF’s, but I may need to draw a ingle triangle which should not do so;
- add an option to show even TEXT boxes in lower TF’s;
- adding freehand objects to be drawn on charts (lines, circles or whatever you may need), considering an object from the beginning of a click till the mouse button i released.
1 user thanked author for this post.
Optimisation done with tick by tick. I used so many hours to optimise variable only to find out it was all done on a single bar. When running the backtest in tick by tick its not profitable. Sametime make tick by tick data awailable all the way historiacally and not only limited
1 user thanked author for this post.
The language documentation needs to be more comprehensive e.g. it does not describe all function inputs, outputs and parameter types. We should not have to work out what these are by trial and error.
1 user thanked author for this post.
Find exclusive trading pro-tools on 
