Ticket #634 (closed enhancement: fixed)
Locking enhancements
| Reported by: | zach | Owned by: | |
|---|---|---|---|
| Priority: | Normal | Milestone: | Backlog |
| Component: | general | Keywords: | |
| Cc: | pablo@…, jeroen@…, doug@… | Forum thread: |
Description (last modified by zach) (diff)
As of JW 5.3, there is a single lock for the player. This lock disables all programatic input (controller rejects input, but controller continues to function normally) until unlock is called.
There are some additional types of locks we may want to investigate. These include:
- Allowing a single plugin to stop / resume playback
- Disable user input visually (grey sheet or indicator on player controls)
- Interrupting setup
- Takeover stage / display area
Change History
comment:4 Changed 3 years ago by jeroen
- Status changed from new to closed
- Resolution set to duplicate
Amended this to #1067.
comment:5 Changed 3 years ago by zach
- Status changed from closed to reopened
- Resolution duplicate deleted
- Milestone changed from Player 5.4 to Backlog
comment:6 Changed 3 years ago by zach
- Description modified (diff)
- Summary changed from Investigate additional locking parameters to Locking enhancements
comment:7 Changed 16 months ago by pablo
- Priority set to Normal
From duplicated ticket 1067:
We talked about adding locking to the javascript API, so let's formalize by adding a ticket
One example that came to mind today is routing the fullscreen button to a JS script that, instead of going fullscreen, draws a lightbox and resizes the player...
Additional parameters
We already have:
Disable programatic input (controller rejects input, but controller continues to function normally)
Make optional:
- Stop / resume playback
- Disable user input visually (grey sheet or indicator on player controls)
- Interrupt setup
- Takeover stage / display area
