1 * how long can UI signal callbacks take to execute? What happens if they block?
2 where ENSURE_CORRECT_THREAD is a macro that is modelled on ENSURE_GUI_THREAD
3 if the handler is not called in the "correct thread", it will use a pseudo-RT-safe-enough technique to get the correct thread to recall "handler" later on, and return.
5 * jog with transport rolling doesn't work properly. My use of ScrollTimeline also doesn't work.
6 * finish button mapping.
7 * concurrency for bank switching? And make sure "old" events aren't sent to "new" faders
9 * removal of a route results in a strip that isn't dead, but doesn't have any effect on the session
10 * use i18n. see string_compose
12 * docs in manual, including button assignment diagram
17 * Generic surface code to common location
18 * bulk remote id changes cause too many surface updates
19 * which bank switching - overlap or dead faders? Option?
20 * signals for buttons?
21 * MackieControlProtocol in namespace Mackie?
22 * power-cycling of surface. fd_midiport doesn't close.
23 * mix busses and/or a "bus-only" bank/mode
24 * what about surfaces like Mackie C4 and BCR2000?
28 * Some indication on the UI of currently bank-switched-in routes?
29 Useful for surfaces that don't have a scribble strip.
30 * use current zoom setting and snap state for shuttle wheel
34 * docs claim that unit will send a host query on init.
35 * test Mackie surface object. Apparently led rings don't work. Stereo busses?
36 * timecode & 55 char displays
42 * get_state isn't called on deactivate. Huh? What did I mean here?
43 * routes "forget" their remote_id between session save and the next session load
44 * definitely something wrong with remote_id assignment on session create
45 (master strip assigned 0).
46 * editor window doesn't update route remote_control_id when it's updated in mixer window.