All these good suggestions on this Thread and for all we know we may be ‘shooting the breeze‘ !?
When was the last time we saw any evidence that anybody from PRT even reads this Thread … let alone progresses any of the ideas?
I suggest that the form below be submitted direct to PRT in addition to posting on here.
Note of info: make sure you use the email address that is registered for your IG / PRT Platform Account else you likely will not get an acknowledgement (that’s been my experience anyway).
https://www.prorealtime.com/en/contact?suggestion=1
I think it’s important they read these suggestions; answering each one would make PRT start a chat thus wasting their time instead of working.
You can tell something has been implemented when a major version is released. If something suggested is added… well that’s great!
Nicolas has always been saying that PRT read this support forum.
I suggest the addition of these 4 keywords:
- SessionOpenDaily
- SessionCloseDaily
- SessionOpenWeekly
- SessionCloseWeekly
to be used in such cases:
DEFPARAM FlatBefore SessionOpeneDaily + 1 HOUR
DEFPARAM FlatAfter SessionCloseDaily/SessionCloseWeekly - 1 BAR
BUY 1 Contract AT MARKET EXITTRADE ON SessionCloseDaily/SessionCloseWeekly
so users would no more be troubled at what time a session closes (for each instrument) and on which day of week.
Have you got a screen shot of what you mean @trevor?
My results are in GBP. but maybe I am misunderstanding what you mean?
If you mean time frame in an MTF strategy the answer is NO.
You should make a local copy of another variable in another TF and work on this.
yes it is for a request for prt
I don’t think they will:
TIMEFRAME(Daily)
ma = average[20]
TIMEFRAME(1 hour)
ma = average[20]
TIMEFRAME(default)
IF close crosses over ma then //which one???
BUY AT MARKET
ENDIF
it would add confusion. Or they should add a qualifier, such as:
IF close CROSSES OVER ma OF Timeframe(Daily) THEN...
but it’s much easier using a copy in case you need to change it.
New idea! In pro screener creation “All crossings” is needed. At the moment there is only ” crosses under” and “crosses over”
Text edit on indicator settings so one can have actual written instructions pop up on indictors to improve decision making.
BelParticipant
New
This would be really helpful IMO as well. Also would be cool to have simpler ways to call current/previous weeks, months, years OHLC like for example WOpen, WHigh, WLow and WClose. Def would be a time saver.
Regards.
I suggest adding optional parentheses “()” BEFORE brackests to BARINDEX.
Now we can write:
BARINDEX or BARINDEX[n]
that could be written also as:
BARINDEX(event or constant[n])
or
BARINDEX(event or constant[n]) [n]
to return the BARINDEX of an event such as:
x = BARINDEX(Close crosses over Average[20])
or:
CrossOver = Close crosses over Average[20]
x = BARINDEX(CrossOver)
to find the barindex of the first crossover starting from the current bar.
or:
x = BARINDEX(CrossOver[1])
to find the barindex of the first crossover starting from the 1st previous bar.
or:
hh = highest[50](high)
x = BARINDEX(hh)
to find the barindex of the highest high over 50 bars.
Adding this OPTIONAL parameter to BarIndex has the advantage of not affecting existing code and not having to add and learn a new keyword.
This addition would be extremely beneficial to programming.
Thanks Roberto, a specific instruction doing the same thing (give the bar number of a previous X occurrence of a condition) will be added. I’m not sure of the keyword and syntax yet, but I know it is on the list.
