Struct MenuEvent 

pub struct MenuEvent {
    pub id: String,
    pub sequence: u64,
}

The menu-activation read surface (frust-reactive’s process-wide menu source — see its module docs): a per-OS desktop shell drains its native menu queue once per frame and reports each activation, and app code observes it here. menu_events() returns the live MenuEvents handle whose latest signal carries a MenuEvent — the activated item’s id exactly as the app wrote it in its MenuSpec, plus a monotonic sequence so choosing the same item twice reads as two activations rather than one stale value.

use frust::{AnyView, Component, Get, any, menu_events, text};

#[derive(Default)]
struct MenuDemo;

impl Component for MenuDemo {
    type State = ();

    fn init(&self) -> Self::State {}

    fn build(&self, _state: &mut Self::State) -> AnyView<Self::State> {
        // A tracked read: this rebuild re-runs when an item is activated.
        let label = match menu_events().latest.get() {
            Some(event) => format!("chose {}", event.id),
            None => "nothing chosen yet".to_string(),
        };
        any(text(label))
    }
}

Available on every target, unlike the MenuSpec vocabulary that describes the menu itself: a component reading menu events compiles on Android/iOS too (where nothing ever pushes one), so shared component code needs no cfg of its own.

Unlike push_deep_link, the push side is deliberately not re-exported: a menu activation has exactly one producer — the per-OS shell that owns the platform menu — and nothing in an app simulates one the way examples/navdemo simulates a warm deep link. One delivered menu activation: the id the app gave the item in its MenuSpec (e.g. "file.open"), plus the process-wide sequence number of this activation (see the module docs). The id is passed through verbatim — mapping it to an action is app code’s job, not this crate’s.

Fields

id: String

The activated item’s app-chosen id, exactly as it appeared in the MenuSpec the shell was configured with.

sequence: u64

This activation’s position in the process-wide activation sequence, starting at 1 for the first push. Strictly increasing, so glue can dedupe by “the last sequence I consumed” and tell a repeat activation of the same id apart from a re-read of the previous one.

Implementations

impl MenuEvent

pub fn new(id: impl Into<String>, sequence: u64) -> MenuEvent

Pair an item id with its activation sequence number.

Public for glue and tests that need to construct the value the signal carries; production pushes go through push_menu_event, which assigns the sequence itself.

Trait Implementations

impl Clone for MenuEvent

fn clone(&self) -> MenuEvent

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for MenuEvent

fn fmt(&self, f: &mut Formatter<'_>) -> Result<(), Error>

Formats the value using the given formatter.

impl Eq for MenuEvent

impl PartialEq for MenuEvent

fn eq(&self, other: &MenuEvent) -> bool

Equality operator ==.

fn ne(&self, other: &Rhs) -> bool

Inequality operator !=.

impl StructuralPartialEq for MenuEvent