scripts: use the new object ID as index in the Lua tables

We cannot guarantee that the object's bound-id is always valid when an event is
triggered, especially when an object is removed. This patch uses the new object
wireplumber unique ID to index Lua tables, fixing runtime WP_PROXY_FEATURE_BOUND
check warnings.
This commit is contained in:
Julian Bouzas
2022-08-23 08:25:16 -04:00
parent 63fbcdc82c
commit 0983326433
2 changed files with 11 additions and 11 deletions

View File

@@ -86,7 +86,7 @@ AsyncEventHook {
next = "register",
execute = function (event, transition)
local node = event:get_subject ()
local id = node ["bound-id"]
local id = node.id
local item
local item_type
@@ -123,10 +123,10 @@ AsyncEventHook {
next = "none",
execute = function (event, transition)
local node = event:get_subject ()
local id = node ["bound-id"]
local item = items [id]
local bound_id = node ["bound-id"]
local item = items [node.id]
Log.info (item, "activated item for node " .. tostring (id))
Log.info (item, "activated item for node " .. tostring (bound_id))
item:register ()
transition:advance ()
@@ -163,7 +163,7 @@ SimpleEventHook {
},
execute = function (event)
local node = event:get_subject ()
local id = node ["bound-id"]
local id = node.id
if items [id] then
items [id]:remove ()
items [id] = nil