Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Re-use previous tournament's settings #209

Open
hero2017 opened this issue Mar 27, 2017 · 9 comments · May be fixed by #706 or #707
Open

Re-use previous tournament's settings #209

hero2017 opened this issue Mar 27, 2017 · 9 comments · May be fixed by #706 or #707

Comments

@hero2017
Copy link

It would be great if when creating another tournament that we wouldn't have to re-enter all the same settings again like PGN output file, Opening Suite, Depth of book, re-adding the engines again and changing its parameters if you don't want to use the global settings for that particular run. It'd be nice if it would use the settings and engine parameters from last time.

Also, it'd save us a lot of working in modifying the saved pgn file if when stopping an unfinished tournament the games with no result wouldn't be saved into the pgn. The way it is now if I start a 200 game tournament but I stop it after a 100 (or whatever) then the pgn will still contain the unfinished game with a "no result" after each game. Makes it hard to post clean pgn's online.

Lastly, the results. I find it horrible that it doesn't list a nice cross-table that also lists the number of wins, losses, and draws for each engine instead of just showing us the elo, games, score%, and draws%

@alwey
Copy link
Contributor

alwey commented May 16, 2017

This request contains 3 different enhancement suggestions.
My 3 x 0.02 €:

first section: +1 (me too). This would save a lot of work for the users and generate some work for the developers.

second section: OK, this makes sense. As a work around for now one may use PGN tools that make it easier to handle this problem.

third section: OK, sure this would be nice to have.

@hero2017
Copy link
Author

I thought my request was being ignored since no comment from Mar. 27. However I'm glad someone else agrees!

@ilaripih
Copy link
Member

Sorry, nothing is ignored, just postponed until I have time to work on Cute Chess again. I've been extremely busy with other projects this year.

@ilaripih ilaripih changed the title Tournament settings not remembered Re-use previous tournament's settings Jul 17, 2017
@ilaripih
Copy link
Member

I'll split points 2 and 3 into new issues. This first one could be implemented by loading the previous tournament's settings by default and having a reset button for using the default tournament settings.

@hero2017
Copy link
Author

Excellent! I can't wait for the release containing these changes.

If I could make a suggestion to help new users better understand; rename the Settings option to Global Settings and instead of a Reset button call it Use Global or something to that effect. Reset to me suggests to clear everything.

Regardless of what you call them I'll be very happy about the new enhancements!

@lordlouckster
Copy link

Nothing has been done for the first issue.

@alwey
Copy link
Contributor

alwey commented Jun 10, 2021

@anonymous7002 You do not know what has been done. Actually, I worked on this topic in 2020 but ran into problems.

@lordlouckster
Copy link

@alwey What sort of problems?

@alwey
Copy link
Contributor

alwey commented Jan 22, 2022

@anonymous7002 @hero2017: My first attempt in 2020 failed by crashing the application.
Now I started from scratch and will come up with a PR this weekend.

alwey added a commit to alwey/cutechess that referenced this issue Jan 22, 2022
Do not delete NewTournamentDialog after usage, but re-use it for the
next tournament.

Add reset functionality to NewTournamentDialog. Only values read from
.ini-file are restored.

Simplify and correct NewTournamentDialog::readSettings.

Resolves cutechess#209
alwey added a commit to alwey/cutechess that referenced this issue Jan 22, 2022
Do not delete NewTournamentDialog after usage, but re-use it for the
next tournament.

Add reset functionality to NewTournamentDialog.
However, on reset use a new NewTournamentDialog.

Simplify and correct NewTournamentDialog::readSettings.

Resolves cutechess#209
alwey added a commit to alwey/cutechess that referenced this issue Jan 22, 2022
Do not delete NewTournamentDialog after usage, but re-use it for the
next tournament.

Add reset functionality to NewTournamentDialog.
However, on reset use a new NewTournamentDialog.

Simplify and correct NewTournamentDialog::readSettings.

Resolves cutechess#209
alwey added a commit to alwey/cutechess that referenced this issue Jan 22, 2022
Do not delete NewTournamentDialog after usage, but re-use it for the
next tournament.

Add reset functionality to NewTournamentDialog.
However, on reset use a new NewTournamentDialog.

Simplify and correct NewTournamentDialog::readSettings.

Resolves cutechess#209
alwey added a commit to alwey/cutechess that referenced this issue Jan 22, 2022
Do not delete NewTournamentDialog after usage, but re-use it for the
next tournament.

Add reset functionality to NewTournamentDialog.
However, on reset use a new NewTournamentDialog.

Simplify and correct NewTournamentDialog::readSettings.

Resolves cutechess#209
alwey added a commit to alwey/cutechess that referenced this issue Jan 22, 2022
Do not delete NewTournamentDialog after usage, but re-use it for the
next tournament.

Add reset functionality to NewTournamentDialog.
However, on reset use a new NewTournamentDialog.

Simplify and correct NewTournamentDialog::readSettings.

Resolves cutechess#209
alwey added a commit to alwey/cutechess that referenced this issue Feb 2, 2022
Do not delete NewTournamentDialog after usage, but re-use it for the
next tournament.

Add reset functionality to NewTournamentDialog.
However, on reset use a new NewTournamentDialog.

Simplify and correct NewTournamentDialog::readSettings.

Resolves cutechess#209
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants