Skip to content
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

made it so that the load and dump functions in the speech.nvgt include also saves if a screenreader should be used or not #88

Merged
merged 3 commits into from
Sep 6, 2024

Conversation

gameTryer
Copy link
Contributor

the change is a bit rudamentary using an if statement to determine the property in question do to me not finding a parse bool function

gameTryer and others added 3 commits August 28, 2024 17:48
… this change takes in to account the users preferense of screenreader enabled or disabled
* any previously saved settings would have caused a runtime error, as the use_sr boolean at position 4 in the array didn't exist in previously saved settings.

* In some cases it's possible that people might want to save multiple different tts_voice objects, and in such cases, they don't want to store the screen reader usage property more than once. Thus, we add a boolean to dump_tts_config, false by default, that can enable this feature.

* We save the use_sr boolean in 1 byte that is 1 or 0, rather than 4 or 5 (true/false)
@samtupy samtupy merged commit db6faa4 into samtupy:main Sep 6, 2024
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.

2 participants