The --method parameter affects only the current "soft thread" (= single
scan), may confuse laymen, and should not matter when an aggregate scan
preset or theme is specified, and those are in general superior and more
encouraged for fc-solve beginners and most experts a like. An aggregate
scan explicitly sets the --method for each scan individually, so there.
As a result, I don't see the point of having the 'Solving method' there.
Perhaps in the future, a more comprehensive GUI for editing the fc-solve
command line will be in order, but that may end up something like thess
monstrocities:
* http://www.codinghorror.com/blog/2006/11/this-is-what-happens-when-you-let-developers-create-ui.html
* http://i.stack.imgur.com/cVWub.gif
* improved startup; progressbar has been shown before load/register games
* improved gettext; game names has been translated during registration
* updated russian translation
git-svn-id: file:///home/shlomif/Backup/svn-dumps/PySolFC/svnsync-repos/pysolfc/PySolFC/trunk@185 efabe8c0-fbe8-4139-b769-b5e6d273206e
* some changes in settings.py: added TITLE, renamed FC_VERSION to VERSION
git-svn-id: file:///home/shlomif/Backup/svn-dumps/PySolFC/svnsync-repos/pysolfc/PySolFC/trunk@184 efabe8c0-fbe8-4139-b769-b5e6d273206e
* added clickable url to About dialog
* many other improvements and bugfixes
git-svn-id: file:///home/shlomif/Backup/svn-dumps/PySolFC/svnsync-repos/pysolfc/PySolFC/trunk@173 efabe8c0-fbe8-4139-b769-b5e6d273206e