Centralization of queries and suggestions on ProRealTime

• 08/10/2019 at 12:38 PM #104516
  GraHal

  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

   

   

  

  GraHal

  Participant

  Topics: 214

  Replies: 8826

  Been thanked: 2198 times
  08/10/2019 at 12:47 PM #104517
  robertogozzi

  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.

  

  robertogozzi

  Moderator

  Topics: 69

  Replies: 17188

  Been thanked: 4064 times
  08/10/2019 at 2:22 PM #104522
  robertogozzi

  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

  1 2 3

  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.

  1 user thanked author for this post.

  Bel

  

  robertogozzi

  Moderator

  Topics: 69

  Replies: 17188

  Been thanked: 4064 times
  08/12/2019 at 9:46 PM #104642
  trevor

  1. Backtest results. Would need to be in $ and points. I do not use points.

  

  trevor

  Participant

  Topics: 13

  Replies: 22

  Been thanked: 1 time
  08/12/2019 at 10:12 PM #104644
  GraHal

  Have you got a screen shot of what you mean @trevor?

  My results are in GBP. but maybe I am misunderstanding what you mean?

  

  GraHal

  Participant

  Topics: 214

  Replies: 8826

  Been thanked: 2198 times
  08/15/2019 at 1:44 PM #104793
  fifi743

  Hello, is it possible to have the same editable variable in several period

   

  

  fifi743

  Participant

  Topics: 10

  Replies: 912

  Been thanked: 424 times
  08/15/2019 at 1:49 PM #104794
  robertogozzi

  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.

  

  robertogozzi

  Moderator

  Topics: 69

  Replies: 17188

  Been thanked: 4064 times
  08/15/2019 at 1:53 PM #104797
  fifi743

  yes it is for a request for prt

  

  fifi743

  Participant

  Topics: 10

  Replies: 912

  Been thanked: 424 times
  08/15/2019 at 2:22 PM #104799
  robertogozzi

  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

  1 2 3 4 5 6 7 8

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

  1	IF close CROSSES OVER ma OF Timeframe(Daily) THEN...

  but it’s much easier using a copy in case you need to change it.

   

   

  2 users thanked author for this post.

  Bel, fifi743

  

  robertogozzi

  Moderator

  Topics: 69

  Replies: 17188

  Been thanked: 4064 times
  09/19/2019 at 12:40 AM #107906
  Pleidian

  New idea!   In pro screener creation  “All crossings” is needed. At the moment there is only ” crosses under” and “crosses over”

   

  

  Pleidian

  Participant

  Topics: 33

  Replies: 56

  Been thanked: 10 times
  09/19/2019 at 11:31 PM #108026
  Vonasi

  Pleidian wrote:

  New idea! In pro screener creation “All crossings” is needed. At the moment there is only ” crosses under” and “crosses over”

  So this then?

  if a crosses under b or a crosses over b then

  1	if a crosses under b or a crosses over b then

   

  

  Vonasi

  Moderator

  Topics: 192

  Replies: 5088

  Been thanked: 1811 times
  10/02/2019 at 8:17 AM #109035
  Pleidian

  Text edit on indicator settings so one can have actual written instructions  pop up on indictors to improve decision making.

  

  Pleidian

  Participant

  Topics: 33

  Replies: 56

  Been thanked: 10 times
  11/27/2019 at 11:59 AM #113719
  Bel

  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.

  1 user thanked author for this post.

  Nicolas

  

  Bel

  Participant

  Topics: 6

  Replies: 57

  Been thanked: 6 times
  12/01/2019 at 9:07 AM #113980
  robertogozzi

  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.

  1 user thanked author for this post.

  Bel

  

  robertogozzi

  Moderator

  Topics: 69

  Replies: 17188

  Been thanked: 4064 times
  12/01/2019 at 11:16 AM #113991
  Nicolas

  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.

  2 users thanked author for this post.

  Bel, robertogozzi

  

  Nicolas

  Keymaster

  Topics: 81

  Replies: 20863

  Been thanked: 4774 times
• Author
  Posts