Skip to content

InstantStateManager has invalid assumption #263

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

Open
Qendolin opened this issue Apr 3, 2025 · 0 comments
Open

InstantStateManager has invalid assumption #263

Qendolin opened this issue Apr 3, 2025 · 0 comments

Comments

@Qendolin
Copy link

Qendolin commented Apr 3, 2025

InstantStateManager assumes that it's always synced, since any changes applied to the input are instantly applied to the config. But this does not hold true if the config value changes through different means. In such cases the UI is desynced and, while it does still sometimes display the correct value, brings all sorts of weird behavior.

Why would the config value change?
In my case I have a list of presets, and a lot of options for each. The 'active' preset is selected from a list (like an EnumController). The other options act on the active preset. So when switching presets issue described above happens.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant