This tries to extract the version automatically, and put the files directly in the
right location
Also fill the tag and name with the version for the github release
Part of #2995
(cherry picked from commit 1286d466e7)
Since commit 7947f233f1a744f5ce9dfdf44372727d4fefb50b in Corrosion,
cmake will default to ${CMAKE_C_COMPILER} for linking a cdylib,
which means that C must be enabled as a language in the project.
Previously, it tried C, CXX, and Fortran and picked the first one.
(cherry picked from commit 87a548a972)
The new version of winit fixes an important bug for macOS Sonoma,
and the bugvix for the workaround won't happen before winit 0.29.
The branch that port to winit 0.29 already removed the workaround
Fixes#3559
(cherry picked from commit 89c269e1b9)
After loading an image with `Image::load_from_path` and setting to a
source property, upon rendering with Skia, it would get replaced with a
Skia renderer specific image representation. When later setting another
image that was also using `ImageInner::BackedStorage`, the property
would not get set because PartialEq::eq would return true because the
image inner types are the same, instead of comparing the vtable
pointers.
Fixes#3510
(cherry picked from commit a7b6bcae6e)
This reverts commit 07f42afef3, but applies
the same change specifically to the Slider, without affecting the
ScrollView.
The scaling up by factor 1024.0 of the min, max and value caused problems
for the ScrollView, which needs these values to match the viewport size
in order to correctly calculate the size of the scrollbar handle.
(cherry picked from commit 7ee17d0914)
Conflicts:
CHANGELOG.md
This new version compiles with LLVM 16 that's now in the GH action
runner windows images.
cc #3365
(cherry picked from commit 779e216b2a)
Conflicts:
.github/workflows/ci.yaml
The problem is that the file stays in the `currently_loading` hashmap
and therefore we thinkg we need to await for the result, while it is not
actually loading
Regression since f1f5a86d0dFixes#3468
(cherry picked from commit c4f83c624d)
The parent is already deleted when we delete the component that is kept
alive by the `grabber` ItemRc in `handle_mouse_grab`
When the ItemRc goes out of scope, we delete the component, but the
parent was already gone.
This doesn't solve a broader issue that we use the parent in many place
and it is not kept alive (for example when using properties of the
parent)
(cherry picked from commit f546d22861)
Implement the partial rendering with winit and our software renderer.
When the background is not opaque, we must still initialize all the
pixel with 0 otherwise we blend over the previous frame.
(That wasn't visible before because the buffer was always empty)
(cherry picked from commit 46ec7875ed)
