George Kiagiadakis 23ba01970f object-manager: use an idle callback to expose tmp globals instead of pw_core_sync ... A core sync is not really necessary here because whatever objects the remote pipewire daemon has to announce have already been sent to us on a message and this message is already being processed at this point. This means, we are not going to be returning to the main loop until all the new objects have been announced and therefore placed into the tmp globals array. So, we can also use an idle callback and achieve the same effect of slightly delaying until all new globals have been announced. With an idle callback, we can be more agile and add those new objects immediately after the message has been processed instead of waiting for a pw_core_sync() reply, which will come in the next message. This fixes an odd failure of the si-standard-link test after applying the fix for #517, which was caused by the fact that the test was previously relying on a delay caused by some unrelated globals being prepared in the object manager that tries to verify the graph state. After those globals were removed from the internal preparation queue, the test would fail to detect the link objects because they were stuck in the tmp_globals array for too long.		2023-10-23 23:14:48 +03:00
..
wp	object-manager: use an idle callback to expose tmp globals instead of pw_core_sync	2023-10-23 23:14:48 +03:00
meson.build	wplua: move under modules/module-lua-scripting	2022-03-24 09:47:59 +02:00