dorne/lib
2025-09-09 11:26:40 +10:00
..
cursed.c test custom curses implementation 2025-09-09 11:25:59 +10:00
cursed.h test custom curses implementation 2025-09-09 11:25:59 +10:00
graph.c test standard ncurses graphing template 2025-09-09 11:26:27 +10:00
graph.h test standard ncurses graphing template 2025-09-09 11:26:27 +10:00
log.c should I just use pipewire's logging? 2025-09-04 11:11:24 +10:00
log.h should I just use pipewire's logging? 2025-09-04 11:11:24 +10:00
main.c experimenting with pipewire api 2025-09-09 11:25:03 +10:00
README.md add C specific README 2025-09-09 11:19:59 +10:00
sine.c example sine ncurses tempalte 2025-09-09 11:26:40 +10:00

A MainLoop that drives the program, reacting to any incoming events and dispatching method calls. Most of a time, the program/thread will sit idle in this loop, waiting on events to occur. A Context that keeps track of any pipewire resources. A Core that is a proxy for the remote pipewire instance, used to send messages to and receive events from the remote server. Optionally, a Registry that can be used to manage and track available objects on the server.