Pages:
Actions
  • #1 by MarkV on 17 Oct 2012
  • Hi Oxa
    There is a small problem with displaying the logs by clicking on the trigger window. The fault seems to be in the “%20” in the trigger name. If you select the dropdown the log then displays correctly. Not sure if this is specific to 7.0.0.39, but I have only just noticed it. The screenshots should be self-explanatory, but do let me know if you need any more info.

    By the way, compliments on the improved layout of the statement. 
  • #2 by mcbee on 17 Oct 2012
  • hi
    this has been a problem before.
    can you get the update to save the constants.
    we have to put all the constants back in our triggers.

    mcbee
  • #3 by redarme on 17 Oct 2012
  • Hi Mcbee

    I found a short term solution that worked for me at least since i upgraded, and that was to save my trigger in two separate locations (once i input the constants again).

    when i opened MFpro and realised the constants were missing again i loaded the backup copy of my trigger and it retained the constants.

    maybe worth a shot if the constants don't appear
  • #4 by pete86 on 18 Oct 2012
  • Quote from: mcbee on 17 Oct 2012, 17:20
    hi
    this has been a problem before.
    can you get the update to save the constants.
    we have to put all the constants back in our triggers.

    mcbee

    I have also lost all my constants in the trigger I was using. The constants for all other ones are still there?.

     Is there something to be done in order to recover the old constants?
  • #5 by Obias-Trader on 19 Oct 2012
  • Hi Oxa,
    There's a problem accessing the sel_index of remembered selections.
    To illustrate this, I set up a trigger this morning to pick remembered selections based on various variables.
    All works fine till trigger asks for the sel_index of remembered selections.
    The attached log file "Lay" will explain. (open with web bowser)

    The condition
    09:51:57|2|22       and Selection's Trigger Expression mysels_market_id_sel_index is greater than 0

    gives
       
    09:51:57|5|103   Alpine Breeze   mysels_market_id_sel_index   245104881   245104881   
    09:51:57|5|103   Sentimentaljourney   mysels_market_id_sel_index   1   1   
    09:51:57|5|103   Bai Zhu   mysels_market_id_sel_index   1   1   
    09:51:57|5|103   Tout Regulier   mysels_market_id_sel_index   1   1   
    09:51:57|5|103   Thats The Deal   mysels_market_id_sel_index   1   1

    instead of returning sel_index as on Betfair of
    2
    1
    3
    4
    5

    What's up with that?
    As you can see if you open the log file in a web browser, all other conditions worked out as expected. It seems to only happen with sel_index.
    I discovered this on exploring my log files in search of why some of my bets didn't fire yesterday.

    Any thoughts? Anybody?

    OT
  • #6 by MarkV on 19 Oct 2012
  • Hi OT / Oxa
    I can confirm the same behaviour as OT reports. I checked sel_index (remembered) on version 7.0.0.39 and 7.0.0.36 and also tried a new profile in both versions.
    sel_id, sel_order, sel_name all work properly, but sel_index does not in both versions.
  • #7 by Obias-Trader on 21 Oct 2012
  • Hi WDS; Oxa; All...
    Spotted another bug.
    The condition:

    Markets -  Number of withdrawn runners -  has not changed

    returns False implying the no. of withdrawn runners HAS changed.
    Checking the race card shows there's been no withdrawals.

    OT
Pages:
Actions