The origin of this proposal is the name of the `swipe-left`, etc.
directional, boolean properties. They're missing another verb in their
name. In principle the right choice would be "recognize". That is what
the type name suggests, that's the term the documentation uses, so the
code should read `recognize-swipe-left: true;`. However that is a long
word. "Handle" is a verb that's simpler. It's also more generic (that's
a downside), but it's otherwise short enough to make things look
"right":
```
SwipeGestureHandler {
handle-swipe-left: true;
swiped => { something.naviate-left(); }
}
```
Therefore this patch proposes to rename the type to SwipeGestureHandler
and prefixes the boolean directional properties with "handle".
My assumption from reading the docs was that the `StandardButton`s
delegated to the root and that the generated callbacks in the root
were to facilitate that behavior.
Fixes#5023
* Implemented resizing for non-decorated winit windows
* Fixed formatting
* Changed direction match to use a tuple, reduced resize border size, returned after handling resize
* Added is resizable check for before resizing winit window
* Added resize-border property to window
* Formatted code
* Change resize-border from float to length
This is the counter-part, which removes focus from the element if it's currently focused. The window - if focused - may still be focused towards the windowing system.
As per API review:
- In the Rust and C++ API we use `set_nine_slice_edges` because the getter couldn't start with 9
- in english we spell number less than 10 with letters and this is a name
As requested in #1462, I've added a `flicked`-Callback that gets
triggered when the `viewport_x`- or `viewport_y` -Properties are changed
by a mouse drag or mouse wheel movement.
Change the double-click implementation to send after two click events
were sent first.
This gets rid of the wait when a double-click handler is installed
before delivering the click.
Trigger the `pointer-event` callback on mouse move. This is of "kind"
Move and the mouse button will always be `Other`, but at least the mappings
will be correct:-)
Closes: #2770
- Use a single code fence for the entire signature. Some where uses the one, some the other format. This unifies to the single fence that's easy to read and avoids extra visual boxes.
- Removed names from arguments as that's not valid syntax at the moment.
- Move the language reference into a sub-section of its own
- Made Reciples & Examples a top-level section
This paves the way for adding more top-level sections, such as advanced topics (with debugging techniques), or the list of supported
platforms.
2023-08-15 10:43:49 +02:00
Renamed from docs/language/src/builtins/elements.md (Browse further)
