Ξ3Participant
Average
Hi Everyone,
I have an interesting question and have not found an answer to it.
I have a graph which is set to use / display 50 units via the (x) units. If I simply graph the BarIndex, on the very first opening of ProRealTime it indicates a number of 63 which means it has loaded 63 bars of which the last 50 are displayed. If I then select 100 units via (x) units, it displays the last 100 bars but seems to load in excess of 500 bars as the BarIndex now reflects more than 500.
My question is whether it is possible to preload a specific number of bars e.g. 100 bars when (x) units is set to 50? The reason being that my indicators use around 80 bars to calculate but I only want to display the last 50 bars. I have tried DefParam PreLoadBars = 100 but it still only returns a BarIndex of 63 on startup.
Any help here would be greatly appreciated.
Ξ3Participant
Average
Sorry all, I meant to say CalculateOnLastBars instead of PreLoadBars as it is required for an indicator (ProBuilder) and not for back-testing (ProOrder). It must be old age creeping in… 😉
Topic moved to ProBuilder support.
Have you found a solution to your problem yet?
Ξ3Participant
Average
Hi Juan,
No luck as yet. In the meantime I have simply created a shortcut key to a 100 bar display (F2) and once loaded I swop back to my 50 bar display (F1).
It is only a problem on initial startup of the ProRealTime platform and once the extra data is loaded it keeps it around. Oddly enough displaying 50 bars tend to load 64 bars of data yet the 100 bar display loads in excess of 560 bars, which is more than enough for the full calculations of my custom indicators I display (need around 80 bars pre-loaded on initial display).
If by chance you do find a solution to this, please let me know and I will repost the solution here. Thanks for the interest!
Unfortunately PRT currently only have a PreLoadBars option for ProBuilder, but perhaps you can write a dummy ‘buy and hold strategy’ and use the graph command to create a pseudo indicator using ProOrder.
The only alternative I could think of is the shortcut method you are currently using.
