Centralization of queries and suggestions on ProRealTime

Forums › ProRealTime English forum › ProRealTime platform support › Centralization of queries and suggestions on ProRealTime

Viewing 15 posts - 271 through 285 (of 364 total)
1 2 3 4 5 … 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
  • 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

     

     

    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.

    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:

    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.
    avatar Bel
    08/12/2019 at 9:46 PM #104642
    trevor
    1. Backtest results. Would need to be in $ and points. I do not use points.
    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?

    08/15/2019 at 1:44 PM #104793
    fifi743
    Hello, is it possible to have the same editable variable in several period

     

    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.

    08/15/2019 at 1:53 PM #104797
    fifi743

    yes it is for a request for prt

    08/15/2019 at 2:22 PM #104799
    robertogozzi

    I don’t think they will:

    it would add confusion. Or they should add a qualifier, such as:

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

     

     

    2 users thanked author for this post.
    avatar Bel, avatar fifi743
    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”

     

    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?

     

    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.

    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.
    avatar Nicolas
    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.
    avatar Bel
    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.
    avatar Bel, avatar robertogozzi
  • Author
    Posts
Viewing 15 posts - 271 through 285 (of 364 total)
1 2 3 4 5 … 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25

Find exclusive trading pro-tools on ProRealCode Marketplace

Similar topics:
buy on certin dates, not on technical singal
buy on retest on a certain candle
prorealtime issues on ig
trailing stop on ib – stop repositioning on dax
2 accounts limitations on ib
2 bars late on entry and exit
autotrading – latent gain will not show on charts
bb trading one long one short on dax 9-17,30
bollinger %b does anyone have the exact code as used by prorealtime
buy on next candle after buysignal

Create your free account now and post your request to benefit from the help of the community
Register or Login