-
Notifications
You must be signed in to change notification settings - Fork 1
Open
Description
I've tried using the OVE-Core API endpoint /sections/{id} to change the space that an existing WebRTC app is in and it doesn't appear to move it successfully. Digging a little I was able to determine that the "state" parameter inside the app parameter does not get reflected in the result. Note that this is different from the "states" (plural) parameter which does indeed appear in the new section.
Current approach is along the lines of what is in this assign_sections function: https://github.com/ImperialCollegeLondon/gridlington-vis/blob/main/app/core_api.py#L66
It works perfectly fine with HTML apps.
Quickly outlining the steps:
- Get existing section details with: GET
"/sections", params={"includeAppStates": True}
- This returns the details with something like this when a session is running
{"id":1,"x":0,"y":0,"w":1920,"h":1080,"space":"LocalNine","app":{"url":"<base>/app/webrtc","state":"ScreenShare","states":{"load":{"sessionId":"<sessionid>","maxSessions":8,"randomSessionId":true,"sessionActive":true,"controllerId":"<controllerid>"}}}}- Note that there is the "state" parameter as well as the "states" one - this is required to define a section as a WebRTC app when setting it up
- Then POST to
"sections/{id}"with the data contained in what was received from the previous GET request but changing the"space"value.
- This works mostly, it sends all of the data but the
"state"parameter is gone and the space doesn't show the webrtc app.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels