Hiddencode with strategies on ProOrder

Forums ProRealTime English forum ProOrder support Hiddencode with strategies on ProOrder

  • This topic has 25 replies, 7 voices, and was last updated 3 years ago by avatargfx.
Viewing 11 posts - 16 through 26 (of 26 total)
  • #156274

    I abusively clicked a Thanks on your post, Vonasi

    Be careful when abusively clicking on things as you could damage your mouse or keyboard.

    Once they have been applied ‘thanks’ cannot be removed so I’ll just have to take it and add it to my total. I did feel it was one of my best posts on the subject of using the wrong language in a forum in a while and so it was probably worthy of praise anyway.

    1 user thanked author for this post.
    #156457
    gfx

    I guess the issue is already known via https://www.prorealcode.com/topic/probacktest-error-parsing/?bbp_reply_to=148907&_wpnonce=5bfced20fa#new-post

    So I won’t create it twice.

    @ Peter,

    Thks for the frustration support 🙂 I always suffer from narrow minded discussions… when the color of the car matters more than the engine…  and also when I have to write complex code to find work arounds to weak native function

    I wish some PRT guys had a look @ Python 🙂

    But I am over now … the newly built strategy, via call functions, runs now on a live account.

    I learnt a lot, which is good even though I am not sure to engage in another PRT project before the TF issue of the CALL command is fixed.

    Wired enough, I build my own debug mode in PRT which sure will help if I had to come again on thatr field.

    Thks to all who provided support.

     

     

     

    #156463

    I always suffer from narrow minded discussions… when the color of the car matters more than the engine…

    That all depends on your exact situation. If you are stuck in a muddy field full of angry bulls then the colour of the car is far more important than the engine. Better not choose red.

    One persons narrow minded discussion is another persons very important point.

    #156464
    gfx

    Lets stay away from angry bulls fields 🙂

    #156466

    Why? I chose a green car. I think it has an engine if that is the noisy thing that makes it move.

    #156483
    gfx

    Appart from the color of your car(s) … has anyone here implemented a ProOrder stategy with IG that triggers indicators using the call function, these indicators being imported as “non modifiable”

    #176379
    Wim

    Yes @gfx, I have. It means distributing multiple files to your “customers”, one modifiable containing the ProOrder strategy code, and one or more non-modifiables containing the “subroutines” alias ProBuilder indicators. The only way I found to protect your Intellectual Property (trade secrets 🙂 ) It works. The pain is in the multi-time-frame part that is only supported in the strategy. I pass the raw MTF-calculation-results via parameters in the CALL for further proprietary calculations in the protected subroutines. I consider this a serious limitation. Another pain lies in the fact you cannot use ProOrder keywords like notonmarket, tradeprice and the like in your subroutines. Subroutines only support ProBuilder language. Again you have to resolve this by passing these values as parameters in the CALL. Another serious limitation. For the time being I stick to ProOrder for automating strategies. But if I wasn’t so damn old, I would be tempted to switch to Python and the IG native API.

    #176416

    PRT should protect the code automatically.

    #176566
    Wim

    Not necessarily automatic. I would prefer to have the choice to protect or not. Having a part of the strategy “unprotected” leaves you with some options, allowing e.g. users of the strategy to modify some parameters like capital available for the strategy or BE-levels. The other issues, no support for MTF or certain ProOrder keywords in called subroutines is a far greater problem. It forces you to all kinds of workarounds, likely to introduce erroneous behavior to your robot.

    #176606

    Yes!

    #176620
    gfx

    ” no support for MTF or certain ProOrder keywords in called subroutines is a far greater problem. It forces you to all kinds of workarounds, likely to introduce erroneous behavior to your robot.”

    like other issues …. no function to retreive account balance, trading system stopped when orders rejected, mandatory single system per account ….  it is a life battle 🙂

Viewing 11 posts - 16 through 26 (of 26 total)

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