Controller scripts need to be able to cross-communicate
Bug #374239 reported by
Sean M. Pappalardo
This bug affects 5 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mixxx |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
Adding this as a wish list item so I/we don't forget...
We need to implement a way for controller scripts to communicate across device instances so that operating controls on one device can have some effect on another when ControlChanged signals aren't involved. (E.g. pressing Deck Swap on one unit would change the currently controlled deck on all units.) So they would pretty much just need to be able to call arbitrary functions in other instances (but the names may be the same since one could conceivably have multiple SCS.3ds attached that all use the same script code, but each has its own ControllerEngine instance.)
Changed in mixxx: | |
importance: | Undecided → Wishlist |
milestone: | none → 1.8.0 |
Changed in mixxx: | |
milestone: | 1.8.0 → 1.9.0 |
Changed in mixxx: | |
status: | New → Confirmed |
Changed in mixxx: | |
milestone: | 1.9.0 → none |
Changed in mixxx: | |
status: | Confirmed → New |
summary: |
- After multiple device support, MIDI scripts need to be able to cross- - communicate + MIDI scripts need to be able to cross-communicate |
Changed in mixxx: | |
status: | New → Confirmed |
summary: |
- MIDI scripts need to be able to cross-communicate + Controller scripts need to be able to cross-communicate |
description: | updated |
tags: | added: communication controllers midi |
tags: | removed: communication |
To post a comment you must log in.
With the current state of the Controller subsystem, I don't think it would be terribly difficult to implement this. We already have unique IDs for each controller, so this should just be a matter of adding methods to ControllerEngine and ControllerEnume rator that allow the CEngine to obtain a pointer to another CEngine instance from the CEnumerator which it could then interact with directly.