The length is an important property of a string and should be available
as a getter. The new size() method is consistent with std::string.
ChangeLog: [C++] Added `SharedString::size()`
- Getting Started is now "Getting Started on Desktop"
- A new "Getting Started on MCU" section combines:
- ESP-IDF
- STM32 (for the board templates we provide)
- Generic (instructions from cmake.md moved here)
The ESP-IDF README is now shortened and links to the C++ esp-idf
section (careful! This might become a dead link if we re-organize
in the future...)
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".
Don't return an Option, just return 0 when the timer is not started.
As discussed in the API review, the rational is that the interval is
just like a field in a struct and when the struct is default
constructed, it is initialized to 0
Run the nightly esp-idf test against the esp-idf slint nightly
binaries, after creating them. The snapshot is run earlier as well
then, so that the tests don't "leak" into the morning working hours.
When cross-compiling CMAKE_EXECUTABLE_SUFFIX may not be set to .exe even
though the host is Windows, because this variable always refers to the
target. This is a missing feature in cmake, so work around it for now.
See also https://gitlab.kitware.com/cmake/cmake/-/issues/17553 I made a
similar workaround in Corrosion long time ago with commit
b8a6b26a0f2d526e0492df9fd88c0495b0b8a64f
The target prop line is duplicated in favor of introducing a variable,
that would otherwise be at risk of being visible in the user scope.
Freestanding implies the lack of windowing system presence and therefore the choice of say Cupertino when building on macOS is not good.
Fluent isn't quite a great choice right now either, as it's not very touch friendly, but it's a compromise :)
