Fix latency field being initially enabled on audio backends not supporting it #9379
+2
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
On platforms where there is at least one audio backend supporting latency (e.g. Windows), the latency field was enabled on all backends, even if they don't support it, though it would become disabled after changing the backend. This also happened after emulation is stopped. The cause was
OnEmulationStateChangednot checking if the backend supported latency;OnEmulationStateChangedis called when the audio pane is first constructed.