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.

Sign up for GitHub

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

Jump to bottom

Consider making a text based amf property interface #32

Open

e00E opened this issue Jun 2, 2022 · 0 comments

Owner

e00E commented Jun 2, 2022 •

edited

Loading

Dealing with OBS' UI code is annoying. We could instead have a text box settings options in an ini key=value fashion.

Advantages:

Simpler code (?)
We can have missing options be completely unset which would be more annoying with UI code as we would have to add a check box "enable this setting" otherwise.
More flexible for future changes in property name and values

Disadvantages:

Less user friendly because a text interface is harder to use and easier to misuse.
Code parsing the text might not end up simpler after all. Considering we want to give reasonable error messages too.

For enums we should allow users to set the underlying integer manually and define it as constants.

We could have the text based interface in addition to the UI interface. But then we do want the checkboxes to disable a setting altogether still.

e00E changed the title ~~Consider making a text based interface~~ Consider making a text based amf property interface

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment