message MenuChoice
Control plane
message MenuChoiceCompositor → the client that asked for a menu: "the user picked this."
The other end of OpenMenu, and the reason that call exists as a pair. A
menu a client asked for is one the compositor has no opinion about: the
ids on it mean something to the process that built it and nothing here, so
the answer goes back where the question came from instead of being acted
on. Everything in between is still the compositor's — the placement, the
grab, the dismissal on a click outside — which is the whole point of
asking for one rather than drawing it yourself.
idl/lava.npidl:680
Fields
serial: u32The serial OpenMenu returned. A client with one menu open at a time can
ignore it; it is here so a stale answer — the menu was superseded while
the reply was in flight — is one a client can recognise rather than act
on.
idl/lava.npidl:685