Think I've cracked the greening stake problem I wanted to solve. I'm no longer using the greening function now Peter, so can't offer any confirmation or not here. Hopefully it's nothing serious.
One thing that I see as the very obvious next step for this beta is the inclusion of the transaction counter in excel.
New beta version of Bet Angel
Andy thanks for your help in sorting this out.Bet Angel wrote:We've just uploaded version 1.23.5 to the downloads area.
This build includes the transaction counter in Excel and also adds additional protection to the code which we believe will avoid the scenario that PeterLe reported.
regards
Peter
PS Nero will be happy with the Transaction Counter! (",)
Thanks a lot for the Excel improvements, they are a big step forward.
One question:
"CLOSE_TRADE closes the open trade on this runner using the current net stake"
- This doesn't mean with greening, right?
If I'm right, would it be possible to make a "Green up" command for single positions just like the Cancel command?
I usually calculate my greening-stakes with Excel, but in case a Close-Order gets filled with a better price than i asked for, there remains a net stake which I cannot green up because it's below the 2€ minimum. A Greening command could solve this problem I think.
Cheers,
Darko
One question:
"CLOSE_TRADE closes the open trade on this runner using the current net stake"
- This doesn't mean with greening, right?
If I'm right, would it be possible to make a "Green up" command for single positions just like the Cancel command?
I usually calculate my greening-stakes with Excel, but in case a Close-Order gets filled with a better price than i asked for, there remains a net stake which I cannot green up because it's below the 2€ minimum. A Greening command could solve this problem I think.
Cheers,
Darko
Andy,Bet Angel wrote:We've just uploaded version 1.23.5 to the downloads area.
This build includes the transaction counter in Excel and also adds additional protection to the code which we believe will avoid the scenario that PeterLe reported.
1.23.5 looks good...been running it all afternoon on two instances; no errors...Thanks
Peter
That's correct, it just looks at the net stake on the runner (total of matched back bets minus the total of matched lay bets), and places either a back or lay bet to ensure the same stake has been placed on both sides.Darko wrote:One question:
"CLOSE_TRADE closes the open trade on this runner using the current net stake"
- This doesn't mean with greening, right?
By 'single position' do you mean you wish to close and green-up just a single bet reference or would you be happy to close and green-up any open positions on that single runner? The latter would be easier to implement and more reliable to use.Darko wrote: would it be possible to make a "Green up" command for single positions just like the Cancel command?
Thanks for your reply. The latter would be totally sufficient for me.By 'single position' do you mean you wish to close and green-up just a single bet reference or would you be happy to close and green-up any open positions on that single runner? The latter would be easier to implement and more reliable to use.
Another issue:
If an Order gets filled after(!) a Cancel Command for an, until then unmatched order,has been transmitted with Excel, Excel currently does not get the information that this order was matched finally. As concequence my Excel-Bot has an open position he does not know about..
Could you think of any way to exclude this case?
Maybe some check up after the transmission of the Cancel Command or after the "Cancel-OK", about the status of this bet ref?
I would also propose that cells P-S remain filled after the Cancel-"OK" appears in the status-cell.It would be helpfull for Order management in Excel, to still have the Bet Ref. after the Order was canceled successfully.
(I used the "Cancel_All" Command for single positions so far, just tested once with "Cancel" to see if cells P-S are also deleted after the "OK" - they are).
Cheers,
Darko
Just had an idea how the last issue I posted could be solved:
If the cells P-S would not be cleared after the Cancel-OK, a "Get Bet" or "Status_Check" command could return the matched-data for odds,stake and time.
People would be able to use "AND(L9="Cancel";O9="OK")" as a trigger for a macro with this "Get Bet"-Command. This could ensure that Excel does not miss a matched bet I think.
If the cells P-S would not be cleared after the Cancel-OK, a "Get Bet" or "Status_Check" command could return the matched-data for odds,stake and time.
People would be able to use "AND(L9="Cancel";O9="OK")" as a trigger for a macro with this "Get Bet"-Command. This could ensure that Excel does not miss a matched bet I think.
The version you're currently using can perform a bet status check - if you enter any bet reference into column R it'll look up the matched stake and average odds and populate columns P & Q. We don't touch the Time (column S) as the bet may have been filled in chunks over a period of time so no single timestamp would be correct.
The facility is really there to give you an ongoing update of the state of an unmatched bet following placement, but you could borrow the facility to lookup the state of any bet on the market at any time.
It makes sense not to clear the cells in columns P to S following cancellation so that you continue to get the bet status update without having to store and re-enter the bet reference.... I'll ask development to modify the behaviour in the next build.
The facility is really there to give you an ongoing update of the state of an unmatched bet following placement, but you could borrow the facility to lookup the state of any bet on the market at any time.
It makes sense not to clear the cells in columns P to S following cancellation so that you continue to get the bet status update without having to store and re-enter the bet reference.... I'll ask development to modify the behaviour in the next build.
Bet Angel wrote:The version you're currently using can perform a bet status check - if you enter any bet reference into column R it'll look up the matched stake and average odds and populate columns P & Q.
That's even better.
Thanks a lot!Bet Angel wrote: It makes sense not to clear the cells in columns P to S following cancellation so that you continue to get the bet status update without having to store and re-enter the bet reference.... I'll ask development to modify the behaviour in the next build.
Installation issue:
Thanks for upgrading further and adding more Excel functionality. I am sure, it will prove very interesting and look forward in playing around with it.
Problem is, I am already thrown back at trying to install the version: Upon running the MSI installer, it gives me a pop up saying "The system cannot open the device or file specified" and upon cancelling then "The installer has encountered an unexpected error installing this package. This may be indicate a problem with this package. [Ha ha - would have guessed so ]. The error code is 2755". And upon a bit of googeling: "I have found that this is a common error when the installer resides on an encrypted volume." - see "http://greystork.com/content.php?id=93". This would hold true for me, my computer has an encrypted hard drive.
Never have experienced this error with previous versions. Might this be something because of the beta version or because you have used a new installer tool kit?
Cheers, Fidibus
Thanks for upgrading further and adding more Excel functionality. I am sure, it will prove very interesting and look forward in playing around with it.
Problem is, I am already thrown back at trying to install the version: Upon running the MSI installer, it gives me a pop up saying "The system cannot open the device or file specified" and upon cancelling then "The installer has encountered an unexpected error installing this package. This may be indicate a problem with this package. [Ha ha - would have guessed so ]. The error code is 2755". And upon a bit of googeling: "I have found that this is a common error when the installer resides on an encrypted volume." - see "http://greystork.com/content.php?id=93". This would hold true for me, my computer has an encrypted hard drive.
Never have experienced this error with previous versions. Might this be something because of the beta version or because you have used a new installer tool kit?
Cheers, Fidibus