Timeline for How can I query the current value of an UCI option?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 18, 2022 at 20:22 | comment | added | ferdy |
After quit and restart, the engine is set to use its default value. We would know the default value through the uci command. Example: option name Threads type spin default 1 min 1 max 512 The default is 1. It is also the current value.
|
|
| Sep 18, 2022 at 20:04 | comment | added | Frank Kremer | I agree that when an UI sent several setoption commands to the engine, the UI knows what it sent. But, as I understand, whenever I quit the engine and restart it later, the setoptions has to reapply, right? So, I'd like to query the current value of an option. | |
| Sep 16, 2022 at 19:49 | comment | added | ferdy | This is not implemented, because you know already what you have inputted to the engine. As an example if I am designing a ui (user interface) if the user sends uci command to the engine, the ui can save this and then sends this to the engine. The engine will reply to the ui and the ui will show this info to the user. When the user asks again the value of option, the ui can just look up the value in the saved values. | |
| Sep 16, 2022 at 16:46 | comment | added | Frank Kremer | The proposal to add an "optionvalues" command is great! I wonder why this is not already implemented, yet! My use case is: I work with defferent engines and want to save the current option values for later use, to reapply them again. | |
| Sep 15, 2022 at 9:08 | history | edited | ferdy | CC BY-SA 4.0 |
added 6 characters in body
|
| Sep 15, 2022 at 1:59 | history | edited | ferdy | CC BY-SA 4.0 |
added 742 characters in body
|
| Sep 15, 2022 at 1:52 | history | answered | ferdy | CC BY-SA 4.0 |