-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathTODO
49 lines (34 loc) · 1.53 KB
/
TODO
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
* = done, - = not done
*- add control to value
- ideally it would be possible to either select an existing
control, or add a control and select that. I suspect the flow
for this inside the UI would be messy. Or not? Just push the
control edit screen?
- log mode on ctors?
UI code rejig:
* three threads
- jack thread, sends mon msgs to ui thread
- ui nonblocking thread, shows monitor data and performs
non-blocking input calls which *look* blocking from the other
thread
- "blocking" ui thread, which handles menu flow and has blocking
calls, which wait for data from the other ui thread.
* classes
- each screen has a display() method, which is called from the
non-blocking thread with a monitor data structure.
- each screen also has a run() method, which does actual flow
within the screen ui, and on exit transfers to another screen.
* data flow
rings:
* jack thread -> ui non-blocking thread
* ui blocking thread -> jack thread
strings and keypresses:
ui non-blocking thread -> ui blocking thread
(this may require condition variables)
mode commands (e.g. "edit a string, please")
- ui-b thread locks mutex, edits an input request structure,
unlocks the mutex and waits on a condition
- ui-nb thread responds (running the appropriate editor or
just keypress input) and when ready, fills in the response
and signals the condition
- ui-b thread continues.