pub fn actions(sent: &Actions, fresh: &Actions) -> Vec<ControlMessage>Expand description
What one connection must be told so its menu matches fresh.
A relabelled action is withdrawn and offered again rather than offered twice:
the client builds a new menu entry on every Add and does not look for
an existing one, so a second Add on a live key would leave the user with
two buttons doing the same thing.
Withdrawals come first for the same reason: a rename must not race its own removal.
REF: references/mumble/src/mumble/Messages.cpp : msgContextActionModify
allocates new QAction per Add and appends it to the context lists;
removeContextAction deletes every entry whose data matches.