Module freya::prelude::dioxus_elements::events

Functions

• onclick
  The click event fires when the user starts and ends a click in an element with the left button of the mouse.
• onfiledrop
  The filedrop event fires when the user drops a file over the element.
• onglobalclick
  The globalclick event fires when the user clicks anywhere. Note that this fires for all mouse buttons. You can check the specific variant with the MouseData’s trigger_button property.
• onglobalfilehover
  The onglobalfilehover event fires when the user hovers a file over the window.
• onglobalfilehovercancelled
  The onglobalfilehovercancelled event fires when the user cancels the hovering of a file over the window. It’s the opposite of onglobalfilehover.
• onglobalkeydown
  The globalkeydown event fires when the user starts pressing any key.
• onglobalkeyup
  The globalkeyup event fires when the user releases any key being pressed.
• onglobalmousedown
  The globalmousedown event fires when the user starts clicking anywhere. Note that this fires for all mouse buttons. You can check the specific variant with the MouseData’s trigger_button property.
• onglobalmousemove
  The globalmousemove event fires when the user moves the mouse anywhere in the app.
• onglobalpointerup
  The globalpointerup event fires when the user releases the point anywhere in the app.
• onkeydown
• onkeyup
• onmiddleclick
  The click event fires when the user clicks an element with the middle button of the mouse.
• onmousedown
  The mousedown event fires when the user starts clicking an element. Note that this fires for all mouse buttons. You can check the specific variant with the MouseData’s trigger_button property.
• onmouseenter
  The mouseenter event fires when the user starts hovering an element.
• onmouseleave
  The mouseleave event fires when the user stops hovering an element.
• onmousemove
  The mousemove event fires when the user moves the mouse over an element. Unlike onmouseenter, this fires even if the user was already hovering over the element. For that reason, it’s less efficient.
• onmouseup
  The mouseup event fires when the user ends the click in an element with the left button of the mouse.
• onpointerdown
  The pointerdown event fires when the user clicks/starts touching an element.
• onpointerenter
  The pointerenter event fires when the user starts hovering/touching an element.
• onpointerleave
  The pointerleave event fires when the user stops hovering/touching an element.
• onpointermove
  The pointermove event fires when the user moves the cursor or touches over an element. Unlike onpointerenter, this fires even if the user was already hovering over the element.
• onpointerup
  The pointerup event fires when the user releases their mouse button or stops touching the element.
• onrightclick
  The click event fires when the user clicks an element with the right button of the mouse.
• ontouchcancel
  The touchcancel event fires when the user cancels the touching, this is usually caused by the hardware or the OS. Also see ontouchend.
• ontouchend
  The touchend event fires when the user stops touching an element.
• ontouchmove
  The touchmove event fires when the user is touching over an element.
• ontouchstart
  The touchstart event fires when the user starts touching an element.
• onwheel
  The wheel event fires when the user scrolls the mouse wheel while hovering over the element.