Gruss Forum • View topic

by **GaryRussell** » Sat Mar 19, 2011 11:16 am

I have fixed it to display the indicator. See http://gruss-software.co.uk/forum/viewtopic.php?p=32417

Please let me know if you still think it's not just a display issue with this version. If you could send me the diagnostic log for this version it would be helpful.

by **Bookmatch** » Sat Mar 19, 2011 12:58 pm

I have carried out the same function on the new amended version and have sent you another e-mail attaching a word document detailing the issues.

by **GaryRussell** » Sat Mar 19, 2011 2:43 pm

The word document explains your problem clearly thank you. I do agree it looks like there is a problem, but I really do need to see the BA_Diagnostic.txt log file. If I also had that file I might have an answer for you now because it could well have contained an error message.

If you haven't restarted BA since can you send me the log file or send it next time it happens. I really think I am close to giving you an explanation, but the diagnostic log contains the key.

by **GaryRussell** » Sat Mar 19, 2011 3:00 pm

I owe you a grovelling apology. I have now replicated your problem. The problem is that fill or update (the code that handles chasing an unmatched stop loss) is not working on the ladder. I have simply been blind to this possibility and all my attempts at replicating your problem have so far been focused purely on the grid. I don't need a log file now and will crawl back in my hole and fix the problem asap.

by **GaryRussell** » Sat Mar 19, 2011 3:44 pm

I have fixed the bug. I won't do an auto update today, but if you want you can install version 1.1.0.66x51 from the link below. Uninstall in Windows control panel first.

http://www.gruss-software.co.uk/Betting ... _Beta2.msi

by **Bookmatch** » Sun Mar 20, 2011 10:27 am

I first suspected there was a issue with stop loss/chase if umatched whilst using the grid. I only noticed the red indicator issue on the ladder at a later date. You have stated that you have fixed the fill or update code in the ladder. Would that fix correct the same issue in the grid?

by **GaryRussell** » Sun Mar 20, 2011 10:59 am

As far as I know there isn't an issue when used with the grid. I've only been investigating the problems you encountered when switching to the ladder. The only way to find out us for you to try it and if you still think there is an issue then please send the diagnostic log and a detailed description as you did before.

by **Bookmatch** » Sun Mar 20, 2011 11:44 am

In the second Word document I e-mailed to you, the lay bet in question was placed using the grid, (as you can see in the transaction log messages) I only switched to the ladder to see if the red indicator had activated. The messages in the transaction log relate to actions taken in the grid. The first screen shot in the document is the one after I had placed the lay bet in the grid. I have never placed a bet in the ladder.

by **GaryRussell** » Sun Mar 20, 2011 12:19 pm

Bookmatch wrote:In the second Word document I e-mailed to you, the lay bet in question was placed using the grid, (as you can see in the transaction log messages) I only switched to the ladder to see if the red indicator had activated. The messages in the transaction log relate to actions taken in the grid. The first screen shot in the document is the one after I had placed the lay bet in the grid. I have never placed a bet in the ladder.

That is the problem I fixed. Whether the bet was placed on the grid or not, if at the time the stop loss is triggered the ladder is displayed then the bug would have stopped it working. Therefore when you had the problem it must have triggered while you were displaying the ladder.

by **Bookmatch** » Sun Mar 20, 2011 12:27 pm

Thank you Gary. Hopefully all of my issues have been resolved. I will continue tentatively and if any other issues arise relating to the contents of this thread, I will forward, via e-mail, screen shots along with the BA diagnostic file as I have before.

by **Bookmatch** » Tue Apr 26, 2011 12:46 pm

Hi Gary.

Settings remain exactly as described in this thread.

After laying a horse and the price coming in to trigger the stop loss, it was subsequently unmatched, but instead of chasing the price down, according to the transaction log, it cancelled the bet without chasing.

by **GaryRussell** » Tue Apr 26, 2011 1:24 pm

If you haven't closed and restarted BA since then please send the BA_Diagnostic.txt file as you did before. Please quote the bet ref of the original lay bet in your email.

Chase if unmatched.

Who is online

Sports betting software from Gruss Software