Enum MouseEventWui 

pub enum MouseEventWui {
    MouseMoveEvent {
        base: MouseEventWuiCommon,
        mouse_leave: bool,
    },
    MouseWheelEvent {
        base: MouseEventWuiCommon,
        delta_x: i32,
        delta_y: i32,
    },
    MouseClickEvent {
        base: MouseEventWuiCommon,
        button: MouseButtonTypeWui,
        mouse_up: bool,
        click_count: i32,
    },
}

Variants

MouseMoveEvent

Mouse move event cef Ref sadly this is not very conclusive. It seems that ‘true’ would generate a mouseLeave event. But this leads to very inconsistent results. Usually an element with onMouseLeave has its event properly triggered even if the moouseLeave argument of the movement was false on the CEF sending side.

WARNING: The argument mouseLeave might be removed in the future. It’s function and CEF docs are inconsistent

NOTE: As far as I can tell it is not really feasible to assume all platform behavior is consistent in its behavior with “special” keys. You are responsible from “holding” the active presses yourself. Internally these are just translated and forwarded.

Fields

base: MouseEventWuiCommon

mouse_leave: bool

MouseWheelEvent

Mouse wheel event Deltas are given in pixels

Fields

base: MouseEventWuiCommon

delta_x: i32

delta_y: i32

MouseClickEvent

Send a mouse click event NOTE: A right click will almost certainly cause a context menu to open on “normal” browsers. The context menu in WUI is “nothing” so it should behave like a normal click. Please report any platform incosistency or special cases that you might encounter.

Fields

base: MouseEventWuiCommon

button: MouseButtonTypeWui

mouse_up: bool

click_count: i32

Trait Implementations

impl Debug for MouseEventWui

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

Formats the value using the given formatter.