Hi,
Sorry if i'm not quite following the rules here but this suggestion has been made in an OLD thread but the suggestion was made with several other suggestions (which have been since been implemented btw)
But anyway, i wanted to make it as a primary and sole suggestion.
Whilst unmatched bets count is very useful it can be limited. I very often find myself wishing that i knew which selection had unmatched bet count.
There is a way around this by coding your own recording to know which selection a bet was placed on etc and seeing if the total of your count matched up with the actual unmatched bets count.
Unfortunately this is limited to people who know how to code (or at least its easier done in vba) and/or sometimes because of the speed of bets being placed and the fact there has to be compensation for communication between BA main and excel that doing this sort of run around can sometimes be inaccurate.
I therefore propose that unmatched bets count be included for individual selections too as well the main 'C' cell total. It can help people out who don't know how to code work arounds to figure out which selection has an unmatched bet and it would definately being far less cpu intensive (tho small doing work around anyway) and quicker. Plus not to mention easier.
I think this could be put in cell T OR get rid of double cell in the name part and place individual unmatched bets under the name of each runner.
Thanks
Individual unmatched bets count
I agree this would be helpful
This would help a little with another issue which is that the P&L that betfair reports for a given selection seems to be a little 'delayed' - i'm not sure if this is betfair API or betangel or both
Currently I use the P&L to work out if i have a bet matched on a selection, but unfortunately as this can be out of date i then place more bets on the selection and become very overexposed! The only way to get round this is for me to code in a bigger delay between placing bets to allow betangel to update the P&L but then you miss out on other selections
The same problem occurs using the unmatched bet count - you still want to place bets on new selections even if you have unmatched bets on others which renders the 'unmatched bet' count fairly useless
thanks
This would help a little with another issue which is that the P&L that betfair reports for a given selection seems to be a little 'delayed' - i'm not sure if this is betfair API or betangel or both
Currently I use the P&L to work out if i have a bet matched on a selection, but unfortunately as this can be out of date i then place more bets on the selection and become very overexposed! The only way to get round this is for me to code in a bigger delay between placing bets to allow betangel to update the P&L but then you miss out on other selections
The same problem occurs using the unmatched bet count - you still want to place bets on new selections even if you have unmatched bets on others which renders the 'unmatched bet' count fairly useless
thanks
HAHA,
Toptrader, are we coding our excels the exact same way. I have the exact same problem which is why i have suggested this in the first place. Every other cell seems to be delayed compared to the status cell meaning you can become overexposed (by the ways we seem to work the market) or you can put in a fail safe delay to counter this problem but then this means our 'reactions' to the market conditions are slower!!
I've been back and forth with BA support for a week now trying to resolve this issue and in the end i've had to settle for a workaround of my own which so far (fingers crossed) seems to be working.
However, of course, i think what i'm suggesting would be a real helper. Thanks for the support in my suggestion.
Toptrader, are we coding our excels the exact same way. I have the exact same problem which is why i have suggested this in the first place. Every other cell seems to be delayed compared to the status cell meaning you can become overexposed (by the ways we seem to work the market) or you can put in a fail safe delay to counter this problem but then this means our 'reactions' to the market conditions are slower!!
I've been back and forth with BA support for a week now trying to resolve this issue and in the end i've had to settle for a workaround of my own which so far (fingers crossed) seems to be working.
However, of course, i think what i'm suggesting would be a real helper. Thanks for the support in my suggestion.