| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
Some GL drivers such as Mesa-D3D12 do not allow one to call SetPixelFormat() on
a given HDC if one pixel format has been already set for it, so first check the
HDC with GetPixelFormat() to see whether a pixel format has already been set
with the HDC, and only attempt to acquire the pixel format if one has not been
set.
This will fix running with GL/NGL on Windows using the Mesa drivers.
|
|\
| |
| |
| |
| | |
gtkplacessidebar.c: add bookmark null checking
See merge request GNOME/gtk!3479
|
| |
| |
| |
| | |
Signed-off-by: Geyslan G. Bem <geyslan@gmail.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This fixes nautilus crash and perhaps other callers issues.
Nautilus (and sometimes glib) crashes with malformed URI inside of the
bookmarks file .config/gtk-3.0/bookmarks when it has no LABEL.
This is result from the closed glib MR #2065 analysis and agreement.
https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2065#note_1091979
Signed-off-by: Geyslan G. Bem <geyslan@gmail.com>
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
docs: Add missing extra files for gdk4 sub-references
Closes #3905
See merge request GNOME/gtk!3481
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The Wayland and X11 references need the gtk-logo.svg and the urlmap.js
extra files.
Fixes: #3905
|
|\ \ \
| |/ /
|/| |
| | |
| | | |
gdk/wayland/cursor/os-compatibility: fix build when memfd_create is not available
See merge request GNOME/gtk!3480
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| | |
available
When building for homebrew/linuxbrew on Ubuntu 16.04, memfd_create() is
not available and causes the build to fail.
This adds a proper check for the function.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
x11: Try harder to find the right monitor
Closes #3900
See merge request GNOME/gtk!3477
|
|/ /
| |
| |
| |
| |
| |
| | |
If we deal with a panel, we end up with no monitor,
and crash, which isn't great and isn't necessary.
Fixes: #3900
|
|\ \
| |/
|/|
| |
| |
| |
| | |
clipboard: Make sure G_TYPE_STRING is nul-terminated
Closes #3899
See merge request GNOME/gtk!3476
|
| |
| |
| |
| |
| | |
Make sure writing a terminating null byte actually works and we don't
just ignore the error message.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When reading text, we need to check we terminate the G_TYPE_STRING
string with a null byte, because the clipboard does not guarantee one.
So just append a \0 to the stream.
Fixes #3899
|
|\ \
| | |
| | |
| | |
| | | |
wayland: Print all layouts in debug spew
See merge request GNOME/gtk!3475
|
| | | |
|
| | |
| | |
| | |
| | | |
(cherry picked from commit 193747fadff285ef7cf921158c454571adece94d)
|
|/ / |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
x11: Fix shadows
Closes #3896
See merge request GNOME/gtk!3473
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Just from reading the code, it seems that we
should unset .csd and .solid-csd at the same
time, since the are mutually exclusive and
we unset them here so realize() can set one
of them again.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The code in gtkwindow.c for dealing with the various
combinations of client-side decorations and client-side
shadows is entirely too complicated.
This commit does not really clean it up, but simplifies
one of the shadow conditions far enough to make some
sense.
With this change, I get the expected decorations in
all the cases I can easily reproduce locally.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Commit a2cd21cab663a003 changed a condition and inadvertedly
broke client-side shadows on X11. Change this back.
Fixes: #3896
|
|\ \ \
| |/ /
|/| |
| | |
| | | |
Mention nightly flatpaks in the README
See merge request GNOME/gtk!3474
|
| | | |
|
|/ / |
|
|\ \
| | |
| | |
| | |
| | | |
a11y: Don't sent redundant property changes
See merge request GNOME/gtk!3472
|
| | |
| | |
| | |
| | |
| | | |
We were sending a property changed event for every set
property whenever we were sending any updates.
|
|\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | | |
gdk: Avoid synthetic motion confusion
Closes #3439
See merge request GNOME/gtk!3471
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Don't emit a synthetic motion event on a surface
that is grab-shadowed by a popup. This has been
known to confuse GTK, at times.
Fixes: #3439
|
|\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | | |
Allow repeated selection extension on gtklistbox
Closes #3887
See merge request GNOME/gtk!3461
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
window: Fix up resize borders
Closes #3856
See merge request GNOME/gtk!3467
|
| | | |
| | | |
| | | |
| | | |
| | | | |
As pointed out by Alberts Muktupāvels, without this,
we are missing the inner edge of the frame.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
The selectors did not apply anymore.
Based on a patch by Alberts Muktupāvels.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Deriving the resize border size from the shadows
carries the risk that we might end up with uneven
resize borders (or none at all, on some sides).
So, justs enforce that we have a big enough shadow
width on all sides.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Make windows resizable in the padding and border
area of the css box as well. This naturally makes
solid-csd borders work again.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The invisible resize borders have been wider than they
should, for a while. Go back to a size close to what
we have in GTK3.
To summarize: resize borders will be at most 12 pixels
on each size, but never wider than the windows shadow.
The resize corners have 'legs' of 24 pixels where you
still get a corner resize cursor.
Fixes: #3856
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Some a11y improvements
See merge request GNOME/gtk!3455
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Whenever we change the :child property, we need to update the
labelled-by relation.
|
| | | | |
| | | | |
| | | | |
| | | | | |
Instead of setting it on its internal child.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Orca needs both events in order to decide whether or not to subscribe to
other event/state changes in a window.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
We're not moving focus here, so we can't rely
on that to conjure the a11y objects into existence.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Only send selection-changed events when we either
had a non-empty selection before, or have one now.
This should help orca speak the right things, and
not the wrong things.
Related: #3549
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Orca uses the window:activate event type to track top levels, and avoid
being spammed by events coming from non-focused windows.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This makes the tabs in about dialogs come out as
'About', 'Credits', and 'System', instead of
'Tab', 'Tab', 'Tab'.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Orca relies on these to keep track of the focus location,
ignoring the focused state. With this change, orca can
once again speak text in entries as I type.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
We are starting with a pretty empty a11y object tree,
and we want orca to bring more of it into existence
by navigating the tree. But that only happens when we
send it events. Primarily focus events, which come in
from GTK via the platform_change mechanism. So realize
the context when we are sending platform_changes,
otherwise, orca never gets the mesage.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
With most context realization happening inside
GtkAtspiContext in response to D-Bus calls, the
code in gtk_widget_realize_at_context that sets
the role is not executed for most accessibles,
causing them to be stuck with the 'filler' role
that makes orca ignore them.
To fix this, split gtk_widget_realize_at_context
into the actual context realization (getting on
the bus) and the setting of widget-specific
properties, and do the latter part when the
widget is rooted.
This makes accerciser report proper roles for
entries and buttons. Orca still has an issue
with getting the hierarchy populated.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Orca ignores events unless the object is inside an object
with role window and states ACTIVE and SHOWING. To arrange
for this, introduce a new ACTIVE platform state, and set it
for windows when they are active.
This gets orca to be a lot more talkative.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Not 100% sure this is necessary, but maybe it helps
to get orca up to speed.
|
| | | | |
| | | | |
| | | | |
| | | | | |
We don't make any use of the cache field, so drop it.
|