Closed kevmo314 closed 8 months ago
I'm just curious, what's the underlying motivation besides this? What issue does this solve? Not that I'm against this, I'd just love to know.
Just mmirroring the get APIs. Right now I poll the get APIs for the same data. Actually to be honest I'd love to see the obs-browser APIs cover all of obs-websocket's capabilities. Using a browser source is a lot more intuitive to many of us and it mitigates the need for port forwarding and dealing with firewalls. I'm building a simple OBS remote at kit.rtirl.com that takes advantage of these APIs :)
Fixed json, manually merging.
Description
This change adds support for obsSceneListChanged, obsTransitionChanged, obsTransitionListChanged events. The event arguments match the signatures of the corresponding getters.
Motivation and Context
Adds additional events for which there are corresponding getters already.
How Has This Been Tested?
Compiled and manually tested.
Types of changes
Checklist: