Pages:
Actions
  • #1 by Oxa (WellDoneSoft) on 04 Jan 2014
  • Bugs fixed:

    1. If manually chosen in Full Mode, selections inactive for auto-trading could become active if the market's prices were not loaded upon adding it to My Markets
    2. In the trigger protection form the program would skip the check on the validity of the entered expiration date, which could result in an incorrect date entered and trigger file protected with a wrong expiration date.
    3. The Global Current Time parameter in a trigger would not work if both date and time were present in the expression.

    Improvements:

    In Time Machine mode, we added a right-click menu item for downloading all markets purchased in a particular folder. So a user can choose to download an individual market, a folder (e.g. a whole day) or all purchased markets.
  • #2 by pcal72 on 04 Jan 2014
  • Thanks Oxa

    All of you are best team ever  8)

    pcal72
  • #3 by pcal72 on 04 Jan 2014
  • Sorry Oxa

    current date/time seems not ok yet, see the picture please.

    pcal72

  • #4 by rubold on 05 Jan 2014
  • A small point, the download page still refers to version 7.1.0.9
  • #5 by Oxa (WellDoneSoft) on 05 Jan 2014
  • Sorry Oxa

    current date/time seems not ok yet, see the picture please.

    pcal72


    That's a puzzle! Can you include a printout from the trigger log window that shows the value of a variable now_time please?
  • #6 by Oxa (WellDoneSoft) on 05 Jan 2014
  • A small point, the download page still refers to version 7.1.0.9
    Thank you rubold.
  • #7 by pcal72 on 05 Jan 2014
  • Hi Oxa

    Hi dont understand what you want.

    But the day was 4/01/2013 and if you see point 5 of my puzze it refers to dezember/2013

    and the condition Current time is grether than 03/01/2014 23:59 is bigger than dezember/2013

    problem is the day i execute this trigger as at 4/01/2014 like you can see in point 3 of my puzzle.

    My idea is close some blocks if today (now_time/current time) is a date bigger than date i define.

    I join trigger to you try.

    Thanks and sorry if its be a litle confusing :)

    pcal72
  • #8 by Oxa (WellDoneSoft) on 09 Jan 2014
  • Paulo, I've checked your trigger file and found the reason why you saw the strange date in the trigger log.

    When you tick the box "Log trigger expressions" in "Betting Options", the program records the value of every trigger expression it encounters.
    It considers each value box in a trigger condition a potential trigger expression, so it records its value into the trigger log file.

    The date/time value you see in your log is taken from the invisible box in the first trigger condition:

    Global Current Time is greater than 03/01/2014 23:59

    If you change "is greater than" to "is between" in this condition, you will see the second field which contains that date and time, 15/12/2013 05:12:02 PM. It must have remained there from the previous version of your trigger when you were doing some tests.

    Anyway, the point is, this value does not affect the program's logic in any way - it is just a value that gets written into the log file. It is not a bug, it is just a piece of information you don't need as you don't use that second value box in the trigger condition.
  • #9 by pcal72 on 09 Jan 2014
  • Hi Oxa

    Thank you for explenation.

    My head have burn last hairs whith this.

    pcal72
  • #10 by Oxa (WellDoneSoft) on 10 Jan 2014
  • I will correct the code so as to not include this bit of trigger expression in the log file if the field is not being used.

    If you experience any other problems with the new version, let me know.
  • #11 by alfaman on 19 Jan 2014
  • I am a little confused now (quite normal!) but can anyone tell me if the memory leak mentioned in BetfairWinner's "Nightmare" thread now fixed in the latest version V7.1.0.10?

    Thanks
     A
Pages:
Actions