| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Recent changes in GTK default input method
makes ~ char to start as dead key, that's
why filechooser stopped detecting it for the
keybinding to open location entry.
Filechooser also installs keybinding to open
location entry on period (.) character, that
was failing too, so we also fixed that.
Fixes #4911
|
| |
|
|\
| |
| |
| |
| | |
Windows: Some fixes to GL context realization (EGL/GLES in particular)
See merge request GNOME/gtk!4386
|
| | |
|
| |
| |
| |
| |
| | |
...when libANGLE is being used on Windows, by checking for a
Windows-specific an ANGLE-specific extension.
|
| |
| |
| |
| |
| |
| | |
As per Benjamin's suggestions, cleanup the previous implementation on
initializing the GLES context on Windows, so that we use more items that are
already in GDK proper and integrate two functions into one.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Instead of first trying to explicitly ask for a WGL 4.1 context, ask for
the WGL context version that matches what is reported via
epoxy_gl_version(), so that we get the maximum WGL version that is
supported by the graphics drivers, and make sure any WGL contexts that
are shared with this (initial) WGL context are created likewise.
We can try to do a default-bog-standard 3.2 core WGL context creation
if the need arises, but let's leave that alone for now.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The EGL context that we are actually creating must have matching OpenGL/ES
versions and allowed GL API set with the previously-created EGL context
that will be shared with it so that they can interoperate together, if
applicable.
This will fix the situation by making sure that we request for the
OpenGL/ES version and OpenGL API set that match with what we have in our shared
EGL context. Otherwise, the newly-created EGL context assumed a OpenGL/ES 2.0
context that supported desktop OpenGL, which may not be what we wanted, such as
in the case of libANGLE.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We are now able to create EGL contexts properly on Windows, but not GLES. This
tries to fix things by doing the following:
* Record the GL context type in a more proper fashion, using an Enum. This
makes things a bit cleaner.
* Force GLES-3.0+ contexts, since libANGLE requires this to properly work with
the shaders-its 2.0 contexts don't work well with our shaders.
|
| |
| |
| |
| |
| |
| | |
Since now we have the shaders working on Windows under GLES with libANGLE using
a 3.0+ context, drop the check to fall back to the Cairo renderer when GLES is
being used.
|
|\ \
| | |
| | |
| | |
| | | |
g-i: mark gtk_text_iter_get_child_anchor as nullable
See merge request GNOME/gtk!4401
|
| | | |
|
| |/ |
|
|\ \
| | |
| | |
| | |
| | | |
Provide GTK DLL as GitLab CI artifact
See merge request GNOME/gtk!4395
|
| | | |
|
|\ \ \
| |_|/
|/| |
| | |
| | | |
gtkimcontextwayland: Remember context on focus-in so enable can happen later
See merge request GNOME/gtk!4397
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Remember the current context on focus-in even though the text-input
isn't set up yet. This helps in the case where the text-input is not yet
created but a widget already got focused. Without that the enable()
invocation in text_input_enter() woulnd't be invoked leaving the input
method disabled.
This fixes
gtk4-demo --run=search_entry
which would initially not show the on-screen keyboard when e.g using
phoc/sway as compositor.
|
|\ \
| | |
| | |
| | |
| | | |
Fix DND hotspot position under Wayland + EGL/Vulkan
See merge request GNOME/gtk!3705
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This makes the hotspot of DND surfaces work when using the Vulkan and
OpenGL renderers.
This bumps the CI image used to the newly built image. This is needed to
install a new enough libwayland-client.so needed for wl_surface.offset.
This is done by adding wayland as a meson subproject, building it
on-demand if the version in the system is not new enough. As
libwayland-client.so is pulled in implicitly when linking to gtk4, the
compile step needs LD_LIBRARY_PATH set to make ld find the right library
to link to.
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
gdksurface-wayland: Fix contradictory assert
See merge request GNOME/gtk!4385
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
gdk_wayland_toplevel_inhibit_idle() contained a contradictory assert
that always fail. More specifically, in the branch that is supposed to
create the idle inhibitor, there is an assertion that it must already
exist and that the refcount must be greater than zero. This causes a
crash on WMs/DEs that use the ZWP idle inhibit manager protocol such as
KDE Plasma and Sway. Fix this by just asserting that the refcount is
zero instead.
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Mark various GskTransform functions as nullable in their return value
See merge request GNOME/gtk!4378
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Various transforms are normalized with their next transform, and if they
end up being the identity transform will return NULL.
For example a translation by (x,y,z) and followed by (-x,-y,-z) will
result in NULL.
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
gtk: document return value of ShortcutFunc
See merge request GNOME/gtk!4389
|
| | | | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
wayland: Don't always restore the saved size when floating
Closes #4634
See merge request GNOME/gtk!4394
|
| | |_|_|/ /
| |/| | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
We only save the size when we transition from floating to fixed, so that
we can restore the size to the one prior to being fixed.
However, we should not restore to this size whenever we see a 0x0 size
from xdg_toplevel, as it can do that any time it doesn't care about the
size, e.g. when the surface is floating and just changing state.
Fix this by only using the saved size when transitioning from fixed to
floating, not when staying floating while previously floating.
Closes: https://gitlab.gnome.org/GNOME/gtk/-/issues/4634
|
|\ \ \ \ \ \
| |_|_|_|_|/
|/| | | | |
| | | | | |
| | | | | | |
Meson: Also query media modules in post-install
See merge request GNOME/gtk!4380
|
| | |_|/ /
| |/| | | |
|
|\ \ \ \ \
| |_|_|/ /
|/| | | |
| | | | |
| | | | | |
reftest: Avoid assertions being compiled out
See merge request GNOME/gtk!4391
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Calling functions inside a g_assert() means those functions will be
compiled out when building with G_DISABLE_ASSERT.
This fixes the release job in the CI pipeline.
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Win32 key events cleanup
See merge request GNOME/gtk!4349
|
| | | | |
| | | | |
| | | | |
| | | | | |
matching
|
| | | | |
| | | | |
| | | | |
| | | | | |
It's unused
|
| | |_|/
| |/| | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
i18n: Detect more translatable attribute values
Closes #4596
See merge request GNOME/gtk!4383
|
| | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
GtkBuilder uses GMarkup, which defines a boolean attribute value as:
- yes/no
- true/false
- 1/0
The ITS file for GtkBuilder UI definitions is only using the first pair,
likely because Glade only ever used those values. GTK's own tools, though,
will typically simplify the full yes/no and true/false strings to 1 and 0,
to minimise the parsing time.
Fixes: #4596
|
|\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | |
| | | |
| | | | |
Fix handling of control characters & remove Win32-specific hacks from gdkkeyuni.c
Closes #2865
See merge request GNOME/gtk!4387
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Make GtkIMContextIME ignore ASCII control characters just like other
IMContext implementations (e.G. GtkIMContextSimple). Fixes bogus
characters appearing in text input fields (old bug 676077).
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The actual code that does the IM context code handling on Windows now uses the
native Windows APIs to handle keystrokes, so this patch is no longer needed, as
it was found that it instead caused issues.
Pointed out in issue #2865.
This reverts commit fd6ce9975e4cc9c090d07e7a6b0013d02b49ce26.
|
|/ / |
|
|\ \
| | |
| | |
| | |
| | | |
IMContextSimple/IMContextIME: Fix AltGr not working on Win32 [GTK4]
See merge request GNOME/gtk!4375
|
| | |
| | |
| | |
| | |
| | | |
The old code assumed that any key press containing Ctrl or Alt cannot be
regular text input. This is not correct on Win32 as AltGr = Ctrl + Alt.
|
| | | |
|
|\ \ \
| |/ /
|/| |
| | |
| | | |
docs: Point source links to the correct branch
See merge request GNOME/gtk!4373
|
| | |
| | |
| | |
| | | |
The default development branch for GTK is now "main".
|
| | |
| | |
| | |
| | | |
The default development branch of GTK is now "main".
|
|/ /
| |
| |
| | |
The default development branch for GTK is now "main".
|
| | |
|
|\ \
| | |
| | |
| | |
| | | |
GdkWin32Keymap bugfixes
See merge request GNOME/gtk!4372
|