Suggestions

[GoogleCodeExporter]

I have a couple of suggestions for improvement. They are not complaints :-) 
AudioSwitch is already very useful.

1. Settings.xml should be stored in %LOCALAPPDATA%\AudioSwitch or some other 
place that is different for different users. It is also considered a bit of bad 
practice to put settings in program folders as those folders should not be 
writable by normal users.

2. Command line arguments could be a bit more logical;

2.a. There really should be a built in help for command line in the program. It 
does not need to be very comprehensive, but at least the syntax should be there.

2.b. Change default for GUI activation. Only start GUI if there are no 
arguments or on specific flag(s), like -gui . Now you have to remember to add 
-x in a lot of cases when you normally don't want a GUI.

2.c. I would like to also be able to use the device names for "-i" argument, 
aside from the index number. Not a big issue :-) 

3. I agree with others that the right button should post a menu with choices 
for settings, exit and such thing.

Original issue reported on code.google.com by bernt.ni...@gmail.com on 28 Aug 2013 at 3:57

[GoogleCodeExporter]

Thanks for these ideas, it's always good to get some criticism, good or bad :)
I'll try to answer them in relation to my opinions, future plans and things 
already done or in process.

1) AudioSwitch started up without any configuration file at all, so I haven't 
payed much attention to it; until now. You are right, it's really how it should 
be done and it's also how .NET default .config files are also handled. Sadly 
they are too limiting in their possibilities to handle custom settings so they 
can't be used. I have an idea where the settings are stored indeed in 
%LOCALAPPDATA% folder, but this should then be copied there by the setup. I 
have understood that there are certain people who always love 
all-things-portable (for ex. www.giveawayoftheday.com users - top suggestion to 
most software), then I'm thinking to make it search it's own folder for the 
settings file and if not found then %LOCALAPPDATA% folder. This would please 
both audiences :)

2) Indeed, they were made with backwards compatibility to command-line usage in 
mind and were not thought through well. I myself have sometimes trouble using 
them while testing them, thus point taken - they must be improved :)

2.a) the default list of commands should indeed printed in response to 
audioswitch.exe -help or /help etc. It's standard behavior really.

2.b) Like mentioned in pt.2, the logic is quite messy right now and this is one 
of those things indeed :)

2.c) Redoing command-line argument parsing this will also be added - nothing 
difficult to do and makes sense when for ex. the order might get messed up 
sometimes.

3) My current local test version already has it - no more F1, right-click gives 
menu with Settings and Exit options. I'm planning to add Help and About dialogs 
as well.

I'm planning to release RC3 at some point with hopefully all these changes done 
and let you guys test it before making a release version.

Sadly google code doesn't provide any forum or similar options so this issue 
tracking will have to suffice. If anyone has a stable forum what they're 
hosting or any suggestions to some general forums where we could host a 
sub-forum for AudioSwitch that would be great! I could add it to front page and 
help people out with any issues, as well as listen suggestions for the future :)

Original comment by tanelte...@gmail.com on 1 Sep 2013 at 11:53

• Changed state: Accepted
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

If you were to use Github (I strongly suggest using git over svn), you'd be 
able to have a pre-made forum for your repository here: http://ost.io/

Original comment by adrianlund on 3 Oct 2013 at 4:16