Skip to content

Store OBS configuration individually per scene collection #106

@inkfarer

Description

@inkfarer

Instead of saving the gameplay and intermission scene globally, save the configured scenes individually for each scene collection.

  • When connecting to an OBS instance or when the scene collection has changed (CurrentSceneCollectionChanged), get the current scene collection along with the list of scenes.
  • If the current scene collection has no configuration defined, notify the user on the Active Match panel.
  • Allow the user to define the scene configuration in the Settings panel as usual, displaying the active scene collection.
    • As obs-websocket doesn't appear to provide a convenient way to get all scenes in all scene collections, we can get by with only allowing the active scene collection to be configured.
  • When a configured scene is found to be missing, clear the deleted scene from the configuration, therefore alerting the user to go back to the settings to fix it.

Footnote: Consider that at a later date, keeping configuration parameters per OBS connection might be desired.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementAdd on to an existing feature

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions