| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
We are using pango api that was introduced in 1.49.1
without ifdefs, so we should require it.
|
|
|
|
|
|
| |
Followup to b244f31337eea. Pango provides color glyph
information for us now, so we don't need to steal a
bit anymore.
|
|
|
|
|
|
| |
Now that text nodes carry flags, we need to compare
them (even though it is very unlikely that they will
differ from node to node).
|
|
|
|
|
| |
Avoid cairo types in the API by introducing a
GskTextRenderFlags enum.
|
|\
| |
| |
| |
| | |
widget: Redraw when font options change
See merge request GNOME/gtk!3917
|
|/
|
|
| |
Its the right thing to do, even if it is a rare event.
|
|\
| |
| |
| |
| | |
gsk: Pass font options down
See merge request GNOME/gtk!3908
|
| |
| |
| |
| |
| | |
Pass the widget's font options along when we
are creating text nodes.
|
| |
| |
| |
| |
| | |
Use the font options from the text node when
looking up glyphs.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The cairo_t that we create to render glyphs for
the glyph cache needs to match the font options
that are supposedly governing how glyphs are
drawn.
Since we allow font options to be different per
widget in gtk, we need to have them at least at
the level of individual render nodes. Adding them
to the lookup key for the glyph cache has the
side effect of solving another problem: We are
not flushing the cache when font options change.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Since font options affect how the glyphs get rendered,
we need to pass the font options down from the gtk level
to where the glyph cache is populated.
Add a new gsk_text_node_new_full api that takes a
cairo_font_options_t in addition to the other parameters.
|
|/
|
|
|
|
| |
Add a toggle for antialiasing, and make the metrics
hinting turn on rounding of positions, to match what
we do with settings now.
|
|\
| |
| |
| |
| |
| |
| | |
Allow custom children on GtkMenuButton
Closes #4205
See merge request GNOME/gtk!3904
|
|/
|
|
| |
Fixes https://gitlab.gnome.org/GNOME/gtk/-/issues/4205
|
|\
| |
| |
| |
| | |
Add a README in gtk/compose
See merge request GNOME/gtk!3916
|
|/ |
|
|\
| |
| |
| |
| |
| |
| | |
reftest-compare: Treat colour channels as undefined if alpha is zero
Closes #4227
See merge request GNOME/gtk!3914
|
|/
|
|
|
|
|
|
|
|
|
|
| |
If the alpha channel is zero, it doesn't matter what the values of the
red, green and blue channels are: the pixel is still fully transparent.
On most architectures, fully transparent pixels end up all-zeroes
(fully transparent black), matching what's in the reference PNG file;
but on mips*el the blend-difference and blend-normal tests get all-ones
(fully transparent white) and a test failure.
Resolves: https://gitlab.gnome.org/GNOME/gtk/-/issues/4227
Signed-off-by: Simon McVittie <smcv@debian.org>
|
|
|
|
| |
(cherry picked from commit 33a4ae12ef268a399d0dad0b205dd87f501b14da)
|
| |
|
|\
| |
| |
| |
| | |
media: Check for gstreamer verion instead of using cc.links()
See merge request GNOME/gtk!3910
|
| |
| |
| |
| |
| | |
This fix error when gstgl_dep comes from a subproject because in that
case it cannot be used in compiler checks.
|
|\ \
| | |
| | |
| | |
| | | |
Add a gtk-hint-font-metrics setting
See merge request GNOME/gtk!3912
|
| | |
| | |
| | |
| | |
| | | |
We have a new setting, so the test that is counting
settings needs an update.
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| | |
This lets people switch back to font rendering that is closer
to what GTK 3 does. It is not perfect - subpixel antialiasing
is not going to work. But it give us an Escape hatch while
we shake out the bugs in our linear layout.
Related: #3787
|
|\ \
| |/
|/|
| |
| | |
Use color glyph information from Pango
See merge request GNOME/gtk!3909
|
| |
| |
| |
| |
| |
| | |
Pango now sets a bit in PangoGlyphVisAttr for
color glyphs, so we don't need to do that
ourselves anymore.
|
|\ \
| | |
| | |
| | |
| | | |
Initial support for new Pango attributes
See merge request GNOME/gtk!3911
|
|/ /
| |
| |
| |
| | |
This is still missing the GtkTextTag hookup,
but it fixes the build.
|
| | |
|
|/ |
|
|
|
|
| |
(cherry picked from commit 9aa08dd1b8b633990ac73efb76d9524f7ded32dc)
|
|
|
|
| |
(cherry picked from commit 7691c94a3732e0349a4c868982159f613d6222dc)
|
|\
| |
| |
| |
| | |
editable: Clarify the docs
See merge request GNOME/gtk!3906
|
| |
| |
| |
| |
| |
| | |
Make it clear that your class must have all the editable properties
already before you call the (confusingly named) function
gtk_editable_install_properties.
|
|\ \
| |/
| |
| |
| | |
Revert "reftests: Enforce default settings"
See merge request GNOME/gtk!3903
|
| |
| |
| |
| |
| | |
Our tests use this settings, so we should respect it
in non-debug builds as well.
|
|/
|
|
|
|
| |
This reverts commit 4e4f57e091020750d66134c212d7778c17d96c20.
This should not be necessary, since we have GDK_DEBUG=default-settings.
|
|\
| |
| |
| |
| |
| |
| | |
Fix Compose handling on big-endian host architectures
Closes #4217
See merge request GNOME/gtk!3902
|
| |
| |
| |
| |
| |
| |
| |
| | |
This adds support for sequences like <Compose>,G,u -> capital G with
breve. Previously, only a capital U was accepted for E, G, I and O
(but a lower-case u was accepted for A and U for some reason).
Signed-off-by: Simon McVittie <smcv@debian.org>
|
| |
| |
| |
| | |
Signed-off-by: Simon McVittie <smcv@debian.org>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The GtkComposeTable cache is always in big-endian format and is
byteswapped on load for the more common little-endian CPUs, but
init_builtin_table() in GtkIMContextSimple can't byteswap the built-in
data without copying it, which is undesirable. Pregenerate both big-
and little-endian compose data, and compile the correct flavour into
each build of GTK. This fixes failure of the composetable test when
building for a big-endian architecture such as s390x and (traditional,
big-endian) powerpc.
Resolves: https://gitlab.gnome.org/GNOME/gtk/-/issues/4217
Signed-off-by: Simon McVittie <smcv@debian.org>
|
|\ \
| | |
| | |
| | |
| | | |
fontbutton: Make sure the window is on the same display
See merge request GNOME/gtk!3901
|
| | |
| | |
| | |
| | |
| | | |
Allow uninitialized GValues to be passed. Makes life easier for the
inspector code I'm writing.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Dragging will just drag the render node.
Dropping will replace the current contents of the textview with the
dropped node.
Neat side effect: You can drag the node onto itself to do a
deserialize/serialize of the current text.
|
| | |
| | |
| | |
| | | |
You can (soon) drag any of the nodes directly into the node-editor.
|
| | |
| | |
| | |
| | | |
Somebody should make this default drag icon machinery pluggable.
|
| | |
| | |
| | |
| | | |
This includes our own new mime type for render nodes, too.
|
| | |
| | |
| | |
| | |
| | |
| | | |
This is needed as GskRenderNode is its own fundamental type and has its
own GValue infrastructure. And I want to put render nodes into the
clipboard which uses GValues.
|
| | | |
|