Version 6.4

Popaya

I found this several days this generally,but I had this to translate :/ .You will have unfortunately to place by hand this probably .This has not possibility to oneself alone it placed on one day.in sense to align alone.

Sory my language

R.

hi
TICK   retrieve data that are not older than, and set to 1 day, this will work.
i think that is what Ronaldinho, was trying to say as well.


mcbee

I made a mistake. In my language "gg ", then hour .

mcbee is right .

Yes thanks mcbee and Ronaldinho thats works. Sometimes its so simple 

hi
today i thought that i would record a race or 2, but found MAYBE a problem.
my trigger is set to back when the lay amount is 25*back amount, but look at the screen shot, it is reversed, the back amount is larger than the lay amount, but the trigger placed a bet.

mcbee

Hi . I from this understand only 25 ... the rest... a bit little information. You would can so that sums so quickly jump simply, and delay bet is  ... here to write can about this a lot ...someone knows something more maybe.

hi
i recorded the full race and played back very slow, the back amount was greater on the back side from 4 secs before the bet was placed.

mcbee

It walks about something like this ? You made this something probably not so. Because this acts what wrote...

hi
mine is the same but with back_amount*24
i will run the new version live and an old version on test, on monday.


mcbee

McBee, I'm attaching a draft trigger that seems to do what you need. Did you check your trigger log files?

hi Oxa
thanks for the reply, but your conditions are the same as my conditions,
i will test for a few days to see what happens, maybe a split second the odds were higher on the lay side.


mcbee

I think also so .It will be main reason 0.02 sec here...

i will test for a few days to see what happens, maybe a split second the odds were higher on the lay side.
mcbee

You can as well check the "variable log file" which should record the exact value of all trigger expressions at the time they were parsed.

hi oxa
there is a mistake in the manual.
MINV(expression1, expression2, ...). Returns the maximum of the two or more expressions listed in the brackets. For example, MINV(-2, 10, 5, 0) will return -2

should say Returns the minimum of the two.


mcbee

should say Returns the minimum of the two.

Just a typo, I think it's something that we could live with.