Foreign Racing Not Settling Properly

Arkle betPos has recently had an issue with Foreign racing not settling properly.
This is due to no SPs being returned on these races.

Some customers have mentioned that these races settle correctly in other bet settling systems.  The reason they do not settle in Arkle, is that for daily SIS supplied racing, we always waiting until an SP was in before settling any selections.  This was to prevent settling in the case of an SP being missed.  We assume the other bet settling systems use the last supplied price and assume it is the SP.  We are amending Arkle to do this for meetings that SIS don’t supply an SP for, but are continuing with our belt and braces policy for UK, IRE races.

Below is our communication with SIS on this issue.

 

With Arkle Feed 2.2.01 and above you should no longer have an issue for the current meetings with no SP (however any new meetings/tracks added may cause problems, unless SIS provide a permanent solution to let us distinguish between an SP race and a non SP race).

 

Rachel,

Is there anything in the SIS event that distinguishes between a meeting that will supply an SP, and a meeting that will not?

At the moment we are just having to hardcode this by meeting name.

This is currently the header information we receive with a meeting.

[SIS DATA SPEC REMOVED FOR CONFIDENTIALITY REASONS]

Rachel O'Reilly

to me, Aoife

show details 14:57 (52 minutes ago)

Hi

I will pass this on to technical for you!

Regards

Rachel

How to send an error report from within Arkle

• While you have the relevant Bet Slip or Error on screen, Type Control + Print Screen at the same time on your keyboard  (This copies the current screen image to your clipboard)
• Help|Send Error Report
• Click on the Add Image button (This pastes the image that is in your clipboard to the error report) 

• Fill in the details of the error within the error description box. (Please include Bet slip ID's and full details of the error within this.)
• You may also need to send us an image of the race result:
• Right click on the relevant selection
• Result|View Result
• Again Type Control + Print Screen at the same time on your keyboard 
• Click on the Add Image button (This pastes the result image that is in your clipboard to the error report)
• Please include Bet slip ID's that link this result image with relevant error report.

• Click: Send Report button(this automatically sends the error report to support@biztechsoftware.co.uk) 
• At this stage you can amend any bets if a customer is waiting. 
• Notify the support team via a messenging program(Skype, MSN Messenger, etc) or by telephone if it is urgent(Urgent = Customers are being served)

Arkle bet POS

Arkle bet POS, is our replacement for Arkle ePos.
When you login you will notice a huge difference on the Home Screen, and windows management.  This difference is mainly a new skin, and much 99% of the functionality is the same.
Previously we used a multi document interface, which contained all the Windows under one main parent window.
We have now go rid of this outdated windows management method.
Now each window is a separate window of its on.  And you can press F3 to go back to the home window, which will have all your menus, that you are used to.
All of your normal menus should be available by pressing F3 and looking at the menu bars on the home window.

Faster Printing
Press F3, and then select the scanner window, in settings check the WPF printing checkbox

Bet Slip Editor Window
We have also rebuilt the Bet Slip Editor Window, from scratch
Image size
If you find that the default image size is too small(or too big). You can resize the image using the Zoom+ and Zoom- buttons. If you want all the images to have the same zoom level that you have just changed, you just need to select Actions/Save Zoom.

• Re-organised the screen, it will take some getting used to, but the layout is much more compact now, and more information is available on the screen.
• New price shortcuts when editing
• Type name + [Page Up] (instead of name + [enter]), this adds the selection and takes price @ scan time guaranteed (instead of having to ctrl + G, and confirm]
• Type name + [Page Down], this adds the selection and takes price @ scan time not guaranteed (instead of having to ctrl + P and confirm]
• If you want to edit the taken price in this scenario, just do ctrl + P or ctrl + G as before

Arkle ePos : Taking Prices Shortcut

QUICK PRICE ENTRY
When entering a selection by name you normal type part of the name and press [enter]
Instead of pressing [enter], you can press [page up], this adds your selection with scan time price guaranteed.
Or you can press [page down],  this adds your selection with scan time price not guaranteed.
Version 2.7.19 or above

Note this currently is not available on entry by number.

Roulette Videos

Roulette Videos

The videos below are samples of the Roulette software. The actual software have much better quality, the videos have been compressed for a better visualization.

 

Wheel Spinning

All possible bets

WPF Snippets

 

Formatting Binded Data Samples

Numeric 2 Decimal Places
Text="{Binding Path=SlipStake,StringFormat=N2}"

Custom date Format
Text="{Binding Path=DateScanned, StringFormat='{}{0:dd-MMM-yy HH:mm:ss}'}"

Implements INotifyPropertyChanged

Implements INotifyPropertyChanged

Implements INotifyPropertyChanged
   Public Event PropertyChanged(ByVal sender As Object, ByVal e As System.ComponentModel.PropertyChangedEventArgs) Implements System.ComponentModel.INotifyPropertyChanged.PropertyChanged

   ' call This when you change a property (also remember to call it ' for read only  properties that use that propered Protected
   Sub NotifyPropertyChanged(ByVal name As String)
       RaiseEvent PropertyChanged(Me, New PropertyChangedEventArgs(name))

   End Sub

 

http://msdn.microsoft.com/en-us/library/system.windows.input.keyboardnavigationmode.aspx

Unable to copy from obj\debug to bin\debug

Arrrrgghgghgh this problem reared its ugly head again today.  Occurs whenever I try to build a solution (winforms) on Visual Studio 2010.

Previously adding this to the build events (My project, compile tab, click build events):
If exist "$(TargetPath).locked" del "$(TargetPath).locked"

But after working for ages I started getting the error again.  Found this online though, and added it and looks like we are good again:

If exist "$(TargetPath).locked" del "$(TargetPath).locked"
if not exist "$(TargetPath).locked" if exist "$(TargetPath)" move "$(TargetPath)" "$(TargetPath).locked"

Microsoft really want to sort this out, as developers typically build a solution more than once, can’t quite get the hang of perfect coding 1st time round yet.