Does this improve or simplify your usage in Blitz as well? Can you give a brief example so that we have a history of the motivation?

I don't have ui-events integrated into Blitz yet. But this allows for two things:

1. Accessing the fields with the . operator. This can sometimes be significantly more ergonomic than destructuring. Notably if you only want to access a single field.
2. Passing the specific event to a function or method. Consider downstream code consuming PointerEvent. Likely there will be a handle_mouse_down method or similar. With the pre-existing design there is no type to pass to such a method (you would have to use a tuple or create your own type). With the new design you can pass a PointerButtonPressEvent (or reference to the same).

(2) is the more significant. However, an example of (1) with a different enum struct-variant from Dioxus:

With struct-variant:

fn map_template_attr(attr: &TemplateAttribute) -> Option<Attribute> {
    let TemplateAttribute::Static {
        name,
        value,
        namespace,
    } = attr
    else {
        return None;
    };

    let name = qual_name(name, *namespace);
    let value = value.to_string();
    Some(Attribute { name, value })
}

With actual struct inside tuple-variant:

fn map_template_attr(attr: &TemplateAttribute) -> Option<Attribute> {
    let TemplateAttribute::Static(attr) else {
        return None;
    };

    let name = qual_name(attr.name, *attr.namespace);
    let value = attr.value.to_string();
    Some(Attribute { name, value })
}