On 09.09.25 20:48, ichthyo wrote:
At that point, I'm at a loss.
The behaviour is logical, yet confusing from a user's perspective.
Yet I see no easy remedy without changing something fundamental.
We do not even have a simple mechanism to hide / destroy the
running UI instance without shutting down Yoshimi.
Meanwhile, Will and I had an exchange of ideas via private mail.
Obviously it is difficult to change the fundamental behaviour,
yet it seems there is a possible workaround:
There is already a set of state flags, which is used to keep
changes from the commandline, which enable / disable GUI or CLI,
separate from the persisted state in the config file.
We could get one step further and always handle it this way,
so that those dangerous changes to disable GUI or CLI would
be persisted, but not immediately take effect in the currenly
running instance.
Thus the flags would get the following meaning:
Config::showGui <-- this is the behaviour in the running instance
Config::storedGui <-- the persistent setting from config
Config::changedGui <-- weather an override / change is pending
and similar for the Cli settings.
Actually this patch is rather simple.
You can see it currently at the tip of my master branch at github
https://github.com/Ichthyostega/yoshimi/commit/2e36bf9d74a8c7f214f1d09ac884b918b0855186
However this is all rather experimental and possibly we'll have
to sleep a night over it and maybe discuss it a bit further.
At least a quick test seems to indicate that the inconsistencies
pointed out by Johannes are resolved with this change.
-- Hermann
_______________________________________________
Yoshimi-devel mailing list
Yoshimi-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/yoshimi-devel
