GUI Playback Display link
Design how the UI
- can connect to the PlayOut subsystem (well, using the facade of course)
- can establish a link or otherwise use the play controller returned as result of creating a play process
- can maintain its own
PlaybackController as a shell to integrate the aforementioned
- can expose and open
Displayer entities
- is able to keep track of these entities to allow sane UI shutdown
This topic is challenging on multiple levels. Our initial dummy player draft clearly highlighted that, we got lots of segfaults, which where almost impossible to track down. It is not sufficient just to stuff things into separate threads, and it is not sufficient just to say "drop it on the floor". We really need to take that "keep track of" thing seriously, and we also need to ensure (as opposed to just hope) not to block indefinitely on shutdown.
Change history
(8)
| blocking: |
733, 951 → 733, 951, 1135
|
| blocking: |
733, 951, 1135 → 733, 951, 1135, 1191
|
| Description: |
modified (diff)
|
| blockedby: |
1098 → 1098, 1226
|
| blockedby: |
1098, 1226 → 1098, 1226, 1289
|
| blocking: |
733, 951, 1135, 1191 → 733, 951, 1135, 1191, 1342
|
| blockedby: |
1098, 1226, 1289
|
| blocking: |
733, 951, 1135, 1191, 1342
|
| Parent Tickets: |
→ 733, 951, 1135, 1191, 1342
|
| Sub Tickets: |
→ 1098, 1226, 1289
|
Migration MasterTickets ⟼ Subtickets-plugin