Default Settings

Currently ChromawebMT has seven user-configurable Default Settings.
They are initially set by us, but they can be reset and Saved by you at any time, either at LogIn or via 'User Defaults' on the main screen's menu bar:

- Maximum Display Stake
- Bet Display Refresh Rate
- Stake / Liability Mode Chooser On each Single Tracker, you can make 'Virtual Bets', and on each Tracker, you can choose whether to make these bets to a hypothetical Stake or to Liability.
- Choose Background Color
- Call Saving Rate
The Call Saving Rate is present as an option if you are concerned that you may be affected by the Betfair Data Request Charging system to be introduced by Betfair on 14 April 2008.
Details of the System are: on the Betfair website
Briefly out Data Call Saving Rate allows you to set a default slower rfresh rate for all but the currently Active Tracker.
Full details of how the Data Call Saving Rate works are at: Betfair Data Charges
- Event Trackers - Show All Runners

By Default Event Trackers open with no Runners selected.
Tick this box if you would prefer them to open with All runners selected.
You can deSelect all or some Runners when setting the options for your Event Tracker. - Event Trackers - 'Traditional' Price
Buttons

By Default Event Trackers open with the 'Traditional' Price Display / Betting Buttons (similar to the Betfair website) visible.
Tick this box if you would prefer event Trackers to open with the 'Traditional' display hidden.
You can Hide or Show the 'Traditional' display at any time while an Event Tracker is running.
- Event Trackers - Maximum Scaling
Buttons

If you usually set Event Trackers to the same Maximum Scaling, you can set a Default on this dropdown.
You can still select a different Scale if necessary when you open Event Trackers
You can change your Defaults, at any time via the Default Settings popup.
Just enter the new value and hit 'Save'.:
Your Defaults are Saved as preferences in the Java Runtime Environment.
This is a new procedure ... previously (before ChromawebMT version 6.1.1), Defaults were saved to an .xml file.
From version 6.1.1, ChromawebMT will not find the old .xml file, so the first time you run it, you should set and save your Defaults anew.
They will then be applied to all subsequent sessions.
Obviously, if you use MTPro on more than one computer, you will have to Save your defaults on each machine.
This is the Refresh Rate for displaying any Bets that you may have on Betfair for the Current Selection(s).
The Refresh Rates for Market Data (current prices, last Matched Price etc) and the Refresh Rate for data about your Matched / unMatched bets need not be the same.
For Market Data, we set an Application minimum refresh rate of 0, which means that, a new request for Market Data will be sent as soon as a response to the previous request has been received.
For Bet Displays, you may not require such a rapid refresh rate (in fact we set an Application default of 3 seconds, but even this may be more frequent than you often need).
Setting the default to, e.g. 5 seconds, will reduce screen flicker, and, depending on the quality of your Internet connection, may reduce 'queuing' of calls to the API server.
There's a 'Bets R/r' (refresh rate) dropdown on each Tracker, where you can adjust the setting, for example if you want to check at an increased frequency to see whether a currently unMatched bet is being matched.
NB the Bet Display Refresh rate has no effect on the speed with which Bets are placed ... just their display!
Obviously, for Back bets, Stake = Liability, but for Lay Bets Liability = Stake * (Odds - 1).
If you prefer to think of your Lay bets in terms of Liability, then you can set 'Liability' as your Default.

