Hi mcbee,
By "separate trigger programs" I mean different .mft triggers.
Is there no way, existing or otherwise that a block can remember which bets were placed for that particular trigger ?
Suppose I set up a trigger called steamer.mft which contained all of the usual triggers like greenup, distribute loss etc .....and ......I had another one called drifter.mft then one day I had the bright idea of combining the two programs.
So, in program A, we have back and lay triggers as well as greenup and dist loss.
in program B, we have lay and back triggers as well as greenup and dist loss
When combined we have back, lay, greenup, dist loss, closing block + lay, back, greenup, dist loss, closing block....... so in total we have 2 programs each consisting of 5 blocks which means a total of 10 blocks..... This whole program could be called
'anything.mft'.......
This terminology "trigger" is a bit confusing as it can mean one of two things.
a) A trigger program eg winningsystem.mft
b) A trigger within one of the trigger blocks of winningsystem.mft
Can you please let me know the correct terms to use when referring to either of them. Perhaps b) should be referred to as a sub trigger.
So, to summarise anything.mft contains 2 main programs steamer.mft & drifter.mft
each of those has 5 blocks.
With all of that said, is it still your opinion that there is no way to keep track of bets placed by each trigger to avoid the " and selections back matched is equal to 0' condition that will prevent a trigger firing or firing when it shouldn't ?
Each bet has a reference or ID number, could that not be used somehow to link that bet with the trigger that fired the bet ?
If all of this is too much just say NO and I'll go back to eating my chocolates
Thanks mcbee
R