mirror of
https://gitlab.freedesktop.org/pipewire/wireplumber.git
synced 2026-06-15 21:58:22 +02:00
3ff9f240c8
after-events hooks will get the original event triggering it, instead of the rescan event. after-events hook can register with any event, but it is called with rescan event info. This is so because, after-events hook run after all the on-events hooks are done with and as a part of the rescan event. so it is triggered with rescan event data, which doesnt carry much info, instead of rescan event, it makes more sense to call the after-events hook with the original event which triggered it. |
||
|---|---|---|
| .. | ||
| core.c | ||
| dbus.c | ||
| endpoint.c | ||
| events.c | ||
| factory.c | ||
| meson.build | ||
| metadata.c | ||
| object-interest.c | ||
| object-manager.c | ||
| properties.c | ||
| proxy.c | ||
| session-item.c | ||
| settings.c | ||
| settings.conf | ||
| spa-json.c | ||
| spa-pod.c | ||
| spa-type.c | ||
| state.c | ||
| transition.c | ||