Cheers for all the input,
Been studying the logs.... I have a set(like 5 or 6) of 'Back' triggers running, all with a different set of conditions.
In Running Horse Racing, there are moments when 2 back triggers fire at once at the same selection, because the conditions of both back triggers are 'TRUE' at that particular moment.
Since I only want ONE back bet/selection(it's a rather substantial amount, not under minimum), I need to find a way to prevent a selection being backed twice or more.
-Slowing down refresh rate is not an option, I need fastest refresh available or I put myself out of the game, IP is like the 'Gunfight @ OK Corral' really....
-Reloading the trigger just once doesn't help either, since it involves 2 different 'back' triggers at the same selection when respective conditions apply.
There is probably some simple solution which I am overlooking.....when you tend to 'dive' in a rather complex set of triggers ( a result of months/years thinkering and trialing) you get the 'tunnel vision' syndrome, or the 'freeze reaction' rabbit in headlights thingy.......... I need some winegums or other mindbroading substances, come on MFP, a free bag of goodies with every subscription!