Skip to content

Implement Derived, Read-Only Settings (to support audio input override)#28

Open
boatmeme wants to merge 12 commits into
mainfrom
audio-settings
Open

Implement Derived, Read-Only Settings (to support audio input override)#28
boatmeme wants to merge 12 commits into
mainfrom
audio-settings

Conversation

@boatmeme

@boatmeme boatmeme commented Jul 4, 2024

Copy link
Copy Markdown
Owner

Because of the observed interaction between the Audio Input Override setting, the Input setting, and a third, as-yet-unidentified byte (assuming it is the true "audio input" value), I saw the need for a concept of a "derived" setting abstraction, which can take the values of multiple, distinct, public-facing settings and use that to calculate a value for its own byte location(s).

I believe it makes sense to build that on top of the existing RetroTinkReadOnlySetting abstraction as these settings/values aren't directly settable by the interface anyway.

After adding the abstraction, I was then able to successfully implement all of the audio settings, including the read-only, derived setting, audio.input.

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

Successfully merging this pull request may close these issues.

1 participant