| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
This is just splitting out a commonly done operation into a macro.
|
|
|
|
|
|
|
|
|
| |
We now always have a "current point" which is either the last point an
operation was made to, or (0, 0) if no drawing operation has
been made yet.
Adding a contour of any kind to the builder will always update the
current point to that contour's end point.
|
| |
|
|
|
|
| |
... and add missing API docs.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
1. Allow specifying the max number of contours
2. Be smarter about creating the paths:
With 10% chance, create a "weird" path like the empty one or only
points or things like that.
Otherwise create a bunch of contours, with 2/3 a standard contour,
with 1/3 a predetermined one.
|
| |
|
| |
|
|
|
|
|
|
|
| |
... and gsk_path_measure_get_closest_point_full().
Those 2 functions allow finding the closest point on a path to a given
point.
|
|
|
|
|
| |
This avoids measuring being too far off (it's still off, but it's less
than a percent now.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Allows querying the coordinates and direction of any specific point on a
path.
|
|
|
|
| |
Adds a circle contour, too.
|
|
|
|
|
| |
Instead of treating bezier curves as lines, we properly decompose them
into line segments now so that we can treat those as lines.
|
| |
|
| |
|
|
|
|
| |
We don't need them yet, but maybe later.
|
| |
|
|
|
|
| |
This allows chunking paths, weeee.
|
| |
|
|
|
|
|
| |
An object to do measuring operations on paths - determining their
length, cutting off subpaths, things like that.
|
|
|
|
|
|
|
|
| |
Instead of the Cairo method and imitating cairo_path_data_t, use the
Skia method and keep points and operations separate.
That way we get a points array that includes the starting point -
because it's always the end point of the previous operation.
|
|
|
|
|
|
| |
... to render the arrow.
The arrow should really be turned into a real thing - maybe an icon?
|
| |
|
| |
|
|
|
|
| |
It's unused in this commit. This just prepares the new object.
|
| |
|
| |
|
|
|
|
|
| |
Take a rendernode as source and a GskPath and fill the region in the
path just like cairo_fill() would.
|
| |
|
|
|
|
|
|
|
|
| |
When the GTK_MEDIA env var is set, check at startup that it works, not
only when the first MeidaFile is instantiated.
This has the fortunate side effect that it prints help output for
GTK_MEDIA=help at startup, too.
|
|
|
|
|
|
|
| |
This allows linking against the static libgtk from the testsuite.
We build the dynamic library by linking all the static libraries into
the final product.
|
|\
| |
| |
| |
| | |
Remove unused static inline function
See merge request GNOME/gtk!3002
|
|/
|
|
|
|
| |
This was causing a warning on AArch64 since __LITTLE_ENDIAN__ and
__BIG_ENDIAN__ weren’t set, but the functions were actually completely
unused.
|
|\
| |
| |
| |
| | |
Fix gtk4-demo’s gears demo on OpenGL ES
See merge request GNOME/gtk!3000
|
| |
| |
| |
| |
| | |
Same issue as the previous commit, int+float is error, and pow() only
works on floats.
|
|/
|
|
|
|
|
|
|
|
|
| |
Here is a command to reproduce this testcase:
GDK_DEBUG=gl-gles gtk4-demo --run gears
Without this patch, Mesa throws this compile error:
0:130(13): error: no matching function for call to `mod(error, float)'; candidates are:
This is caused by `u_rotation - 90` being of type error since
`u_rotation` is a float and it’s illegal to subtract it with an integer.
|
|\
| |
| |
| |
| | |
Wip/otte/for master
See merge request GNOME/gtk!2997
|
| |
| |
| |
| |
| |
| |
| | |
If set to TRUE, does not call the free func for the removed items.
This can be used to move items between arrays without having to do the
refcounting dance.
|
| |
| |
| |
| |
| |
| |
| | |
Use the horizontal policy for horizontal decisions, not the vertical
one.
This broke in 0011ce949c3580e02c4b2c3d83584a6c6e82090c.
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
This fixe video sources with longer loading times not automatically
playing.
|
| |
| |
| |
| |
| |
| |
| |
| | |
1. That's a bad idea UI wise as you can't see the search after you
scrolled.
2. That's a bad idea code-wise because Listviews need to be put into
a ScrolledWindow or they won't scroll.
|
| |
| |
| |
| |
| |
| | |
Invalid matrices are okay in GSK (and GL), but not in Cairo.
Testcase included.
|
| | |
|