Hello there,
I've got a little query that I can't find an answer for anywhere in ther help or on the forum. I would like to be able to launch BA in such a way that both my settings and screen defaults are identified via the command line. i.e.
C:\Program Files (x86)\Bet Angel Limited\Bet Angel - Professional\BetAngle.exe -display BackDefault -settings BackRegular
Does such a paradigm exist and if not, would it be possible to showhorn it into a future build?? The reason for this is that I have automated the creation of the markets.cfg file via a webservice and small helper app and have several instances that use different rules with different markets.cfg files. By allowing these parameters to be set on the command line, i'd be able to fully have a HANDS OFF setup for each of my rule sets and would only need to double click my app (with these parameters) at the start of each session for each rule -and bingo..
hope this is doable.
[edit] - just highlighting another thread where the OP looking for a similar startup commandline approach:
viewtopic.php?f=20&t=14624&p=136102&hil ... ne#p136102
Bet Angel - Command Line parameters
I would think that's possible - might be some restrictions such as the profile names can't include a space or something like that. We can look into it.
One thing I will point out though is that you'd still have to manually enter your password on the login screen. There's no way betfair would allow any application the supports the storage of a password (even if it's in the command line properties).
One thing I will point out though is that you'd still have to manually enter your password on the login screen. There's no way betfair would allow any application the supports the storage of a password (even if it's in the command line properties).
yeah completely get that (re BF) - arriving on the login screen with the defaults filled out actually would (for such a minimal change) be a HUGE workflow saver!! I'm certain I'm not the only one that would benefit and would be happy to create a small post to highlight the various use cases it could be put to...Bet Angel wrote: ↑Tue Oct 02, 2018 4:51 pmI would think that's possible - might be some restrictions such as the profile names can't include a space or something like that. We can look into it.
One thing I will point out though is that you'd still have to manually enter your password on the login screen. There's no way betfair would allow any application the supports the storage of a password (even if it's in the command line properties).
cheers and thanks
FYI - i had been getting round the command line issue by writing out a bespoke comms.cfg file as part of my app launch, but obviously, this requires other plumbing code/overhead and is brittle to future enhancements to this file content..
The general release of v1.51.1 (now on the download page) contains those command line parameters to prefill the profile options on the login screen.
So you've got :-
/SETTINGS:profile_name
/LAYOUT:profile_name
If your profile name happened to contain a space, then you'd put the name in quotes. e.g. /SETTINGS:"profile name"
So you've got :-
/SETTINGS:profile_name
/LAYOUT:profile_name
If your profile name happened to contain a space, then you'd put the name in quotes. e.g. /SETTINGS:"profile name"
sorry, was just watching bake off!! brilliant, thanks so much for that -appreciated.. this will be of HUGE benefit for those that run multiple sessions.Bet Angel wrote: ↑Tue Oct 09, 2018 8:59 pmThe general release of v1.51.1 (now on the download page) contains those command line parameters to prefill the profile options on the login screen.
So you've got :-
/SETTINGS:profile_name
/LAYOUT:profile_name
If your profile name happened to contain a space, then you'd put the name in quotes. e.g. /SETTINGS:"profile name"
/THANKS_AGAIN
Morning... Tried to implement this new feature as part of my current process, but alas have come unstuck. I'm using System.Diagnostics.Process along the following lines (cut down example from my working code):
Although BA launches as expected, neither of the parameters are actioned. Both named parameters exist as saved settings. I'm not sure if there's some sort of clash going on as I can't debug down to the level of the parameters being passed in. I *have* to use the arguments in this manner as they are dynamically derived from a webrequest in another part of the process, thus can't hardcode a set of shortcuts with the arguments.
Hopefully you'll be able to use the above example as a test bed.
cheers
jim
Code: Select all
const string filePath = @"C:\\Program Files (x86)\\Bet Angel Limited\\Bet Angel - Professional\\";
string settingsName = "BackSet3";
string layoutName = "Standard";
var processBa = new System.Diagnostics.Process
{
StartInfo =
{
// required path as well as exe name!!
FileName = filePath + "BetAngel.exe",
WorkingDirectory = filePath,
Arguments = string.Format(@"/SETTINGS:{0} /LAYOUT:{1}", settingsName, layoutName),
}
};
processBa.Start();
Hopefully you'll be able to use the above example as a test bed.
cheers
jim
hmm- maybe i was a complete n00b and FORGOT to download the latest version on my dev server . will keep you posted.
ok,i did a complete fresh installation and although it's reporting as v1.51.1, the timestamp is 26/09/2018 15:40. hope you can help
[edit] - my bad, was downloading the beta, rather than the genral release BAP_1_51_1.exe - sorted now and working perfectly!! lol
[edit] - my bad, was downloading the beta, rather than the genral release BAP_1_51_1.exe - sorted now and working perfectly!! lol
i had a word with the devs on this point (login details) and betfair make it very clear that usernames and passwords should not be stored and made accessible to any API based commercial application (even if on the command line) due to security reasons. would have been nice tho - even better if a complete silent login!!