Advice on combining conditions

Forums › ProRealTime English forum › ProScreener support › Advice on combining conditions

Viewing 15 posts - 16 through 30 (of 48 total)
1 2 3 4
  • 11/06/2017 at 4:05 PM #51672
    thetragiccircle

    Yes, you are totally correct and I am wrong…..I see the error of my ways and it is because the { and the [ are on the same key, and with my poor eyesight, I did not notice !

     

    11/06/2017 at 4:43 PM #51687
    thetragiccircle

    In the 6th post to this thread, dated October 23rd at 4.35, you replied following my query concerning the possible flagging of any returning signal as a long ( ) or short (-)

    This is the result of combining the two indicators, though you can only return ONE criteria and there’s no way to change the displayed data to tell between long and short.

    In the screenshot below is an example of a screener I already have,  where it is proprietary and unfortunately entry to the code is prohibited, but in the Proscreener table, it does show the name of the screener (ie Porsche3.0), …I have also circled where it has returned 2 short signals by means of a – prefix, whereas the long signals have none.

    Can you direct me to anywhere in an instruction manual where I could learn how to modify the screener which you joined together for me, so I could add its name in the area similar to the screenshot below, and also to prefix a minus sign to a short signal return?

    Thanks again

    David

    11/06/2017 at 5:07 PM #51703
    Nicolas

    You can make a new variable that will make the sorting criteria depending of the signal type (long=+1 or short=-1):

     

    1 user thanked author for this post.
    avatar thetragiccircle
    11/06/2017 at 5:53 PM #51715
    thetragiccircle

    Brilliant, thank you so much…does this variable get added as it is to the area where I have circled after the last line?, ie at the end?

    11/07/2017 at 10:14 AM #51764
    thetragiccircle

    As per my last post..here is the code to which I wish the new variable attached, to return a -1 for short and 1 for long signal. Thanks

    11/07/2017 at 10:17 AM #51765
    thetragiccircle

    Sorry to be complicated but is there a code for adding my name of the screener in the box at the top of the proscreener table as in my screenshot at 4.43 yesterday? I would like to add the name “Lotus15” if at all possible. Thanks yet again. David

    11/07/2017 at 10:57 AM #51774
    robertogozzi

    You just have to name your screener the same as the text you want to be displayed.

    1 user thanked author for this post.
    avatar thetragiccircle
    11/07/2017 at 1:34 PM #51808
    thetragiccircle

    Sorry I dont understand that, I have named my screener as such but it does not appear in the proscreener table, for example in the bar as in the attached screenshot.

    Compare that to the attachment P1 at 4.43 yesterday…that is what I am trying to acheive, as well as trying to figure out where to put the variable code to return -1 for short signals and 1 for longs as per the post at 5.53 yesterday.

    Thanks again

    11/07/2017 at 3:37 PM #51827
    thetragiccircle

    I asked…S.orry I dont understand that, I have named my screener as such but it does not appear in the proscreener table, for example in the bar as in the attached screenshot.

    I think I now see it……Does that mean the screener name goes into the last line between brackets, starting “Variation AS….”?

     

    11/07/2017 at 3:42 PM #51828
    robertogozzi

    You can use that part if the name, if the name of thye screener box above is not what you want, as I hilightened in the attached pic.

    1 user thanked author for this post.
    avatar thetragiccircle
    11/07/2017 at 4:18 PM #51833
    thetragiccircle

    Thanks Roberto….its not important I suppose…no need to have it there twice !

    Any advice on the short/long variable?

    11/07/2017 at 6:10 PM #51847
    robertogozzi

    I could not suggest more than Nicolas said and wrote!

     

    1 user thanked author for this post.
    avatar thetragiccircle
    11/07/2017 at 6:39 PM #51849
    thetragiccircle

    Thank you, but you cannot tell me where to place the variable within the code? (see posts 5.07, 5.53 yesterday and 10.14 today)

    11/07/2017 at 7:13 PM #51851
    robertogozzi

    Ok, that’s how it should go, please try and let me know:

    1 user thanked author for this post.
    avatar thetragiccircle
    11/07/2017 at 7:56 PM #51853
    thetragiccircle

    Hi Roberto, I have tested it and it is not returning short signals only longs. Is line 15 in the correct place?

     

  • Author
    Posts
Viewing 15 posts - 16 through 30 (of 48 total)
1 2 3 4

Find exclusive trading pro-tools on ProRealCode Marketplace

Similar topics:
buy on certin dates, not on technical singal
trailing stop on ib – stop repositioning on dax
10ema/30ema crossover on weekly charts?
2 accounts limitations on ib
array support resistance buy on midlevel
automatic trading on ib stocks and etf
build ea bassed on indicatir
buy and sell conditions
buy and sell conditions
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