Set grouping on-device

[jakemoves]

From the Cohort UI overlay screen, a show technician should be able to select a grouping for the device. This device should then only play cues specifying that grouping or "all".

Unity Editor

• add serialized array for possible groupings ["all", "marco", "gemma", "roslyn"]
• under 'ordered cuelist', add dropdown to each element to select grouping for cue (default to "all")
  • this struct is "CueReference"

Unity Client

• [x] dropdown for UI
  • hardcoded options from editor
  • updates the CHSession on the device
• [x] Next asset and Previous asset buttons should navigate through the ordered cuelist, filtered to cues with groupings that are either "all" or the current device grouping
• [x] Play and Stop buttons should send JSON message with grouping as targetTags: ["all"] (or whichever grouping is set in the ordered cuelist)
• [x] Cues include a property called "targetTags". A device should play any cues it receives that match its grouping. ("All" is a special case but I think it's mostly handled the same way.)

[jakemoves]

'all' grouping

Jake wrote this poorly, here's a revised spec:

• 'all' grouping is a superset of all specified groups
• cues with grouping 'all':
  • should play on every client that receives them
  • should appear in the ordered cuelist for any specified grouping

[jakemoves]

Grouping index vs. labels

• currently in the ordered cuelist, groupings are set with an integer index
• this would be friendlier as a dropdown or multi-selectable radio buttons
• but dropdowns can only be powered by an enum, which is static in-code
• Odin Inspector is a commercial product that would allow this, $55
• or custom editor code
• we'll wait and see if it's rough for technicians to use before mitigating

[jakemoves]

Scrolling images

• feels janky / frame-y on iOS (will upload)
• @spots97 to spend an hour or two researching / going deeper

[jakemoves]

Portrait mode for Cohort UI

• player settings: portrait support
• UI should be easy to use for a performer using one hand in portrait mode
• likely visual hierarchy / importance: Play, Next, Stop, Prev
• temporal order: next/prev is like forward/back
• don't forget the label display area
• check for weird interactions with cue content (images flipping with the device etc) — cue content should not be affected when audience member rotates device
• @spots97 to implement