Expand description
Elements, attributes and events definitions.
Modules§
Structs§
imageelement let’s you show an image.labelsimply let’s you display some text.paragraphelement let’s you build texts with different styles.rectis a generic element that acts as a container for other elements.svgelement let’s you display SVG code.textelement is simply a text span used for theparagraphelement.
Functions§
- The
clickevent fires when the user starts and ends a click in an element with the left button of the mouse. - The
filedropevent fires when the user drops a file over the element. - The
globalclickevent fires when the user clicks anywhere. Note that this fires for all mouse buttons. You can check the specific variant with theMouseData’strigger_buttonproperty. - The
onglobalfilehoverevent fires when the user hovers a file over the window. - The
onglobalfilehovercancelledevent fires when the user cancels the hovering of a file over the window. It’s the opposite ofonglobalfilehover. - The
globalkeydownevent fires when the user starts pressing any key. - The
globalkeyupevent fires when the user releases any key being pressed. - The
globalmousedownevent fires when the user starts clicking anywhere. Note that this fires for all mouse buttons. You can check the specific variant with theMouseData’strigger_buttonproperty. - The
globalmousemoveevent fires when the user moves the mouse anywhere in the app. - The
globalpointerupevent fires when the user releases the point anywhere in the app. - The
clickevent fires when the user clicks an element with the middle button of the mouse. - The
mousedownevent fires when the user starts clicking an element. Note that this fires for all mouse buttons. You can check the specific variant with theMouseData’strigger_buttonproperty. - The
mouseenterevent fires when the user starts hovering an element. - The
mouseleaveevent fires when the user stops hovering an element. - The
mousemoveevent fires when the user moves the mouse over an element. Unlikeonmouseenter, this fires even if the user was already hovering over the element. For that reason, it’s less efficient. - The
mouseupevent fires when the user ends the click in an element with the left button of the mouse. - The
pointerdownevent fires when the user clicks/starts touching an element. - The
pointerenterevent fires when the user starts hovering/touching an element. - The
pointerleaveevent fires when the user stops hovering/touching an element. - The
pointermoveevent fires when the user moves the cursor or touches over an element. Unlikeonpointerenter, this fires even if the user was already hovering over the element. - The
pointerupevent fires when the user releases their mouse button or stops touching the element. - The
clickevent fires when the user clicks an element with the right button of the mouse. - The
touchcancelevent fires when the user cancels the touching, this is usually caused by the hardware or the OS. Also seeontouchend. - The
touchendevent fires when the user stops touching an element. - The
touchmoveevent fires when the user is touching over an element. - The
touchstartevent fires when the user starts touching an element. - The
wheelevent fires when the user scrolls the mouse wheel while hovering over the element.