| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
| |
gtk-doc behavior changed, it seems, and these options now
cause the build to break.
|
| |
|
|
|
|
|
|
|
|
| |
The :last-child selector supposed to reset the border was
overridden by the :hover selector. This is fixed by moving the
:last-child selector after the overriding one.
Thanks to Sebastian Keller for spotting.
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=779078.
|
| |
|
| |
|
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=779653#c33
and this is closer to what gtk-3-22 says anyway.
|
|
|
|
| |
The rest of the ui file follows that convention.
|
|
|
|
| |
commit 5729ea7744c2a41ae8fb833db6690a6aa5ad7a84 skipped these
|
|
|
|
|
|
|
|
| |
…erties clobbered by commit c92b7d4224b9cef1d08373fcc28f7fbd96c64e6d.
That and its counterpart were for removing :expand and :fill child props
from GtkBox, but they ended up catching these for GtkToolItemGroup too.
While GtkToolItemGroup still has these, we may as well keep demoing them
|
| |
|
|
|
|
|
|
| |
Fix the sizing and spacing, blue tags for the bright variant,
similar to what gnome-documents was shipping, and inverted gray
tags for the dark variant, not vanishing on hover.
|
|
|
|
|
|
|
|
|
| |
It was only testing the default configuration, where overlay scrolling
is on and both scrollbars use POLICY_AUTOMATIC. We should also test the
other 3 configurations that are available by including non-overlay
scrollbars and/or those that use POLICY_ALWAYS.
https://bugzilla.gnome.org/show_bug.cgi?id=778853
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
POLICY_AUTOMATIC means scrollbars are only shown when needed, i.e. when
the size of the window is not large enough to show the entire child. So
when measuring the preferred size, such scrollbars should be ignored.
But measure() added size for *any* non-overlay scrollbar of the opposite
orientation, e.g. for horizontal size, it added the width of vscrollbar.
So we requested for child + bar, & having enough for child meant that the
policy hid the bar, leaving extra space empty below/right of the child.
Fix this by only adding size for such bars if they use POLICY_ALWAYS.
https://bugzilla.gnome.org/show_bug.cgi?id=778853
|
|
|
|
|
|
|
|
|
| |
• Only calculate the specified dimension – rather than measuring both &
discarding the other (which will often be recalculated right after)
• Only measure a given child scrollbar if it may be visible, not always
• Move variables into narrowest scopes & otherwise improve readability
https://bugzilla.gnome.org/show_bug.cgi?id=778853
|
|
|
|
| |
The standard atom is UTF8_STRING.
|
|
|
|
| |
It measured horizontal size when it needs height, making the test fail.
|
|
|
|
|
| |
Meson has a `--buildtype` option which allows us to avoid defining an ad
hoc `--enable-debug=yes|no|minimum` option ourselves.
|
|
|
|
| |
The `declare_dependency()` for GIR does not need a `link_with` argument.
|
|
|
|
| |
It does not pass, but at least we can check it.
|
| |
|
|
|
|
|
|
|
|
|
| |
Some files that this script will process might have UTF-8 items in
there, which can cause problems on Python 3.x as it is more strict and
careful on unicode issues. Fix this by:
-Doing what we did before on Python 2.x
-Opening the file with encoding='utf-8' on Python 3.x
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The user data passed when exporting a Wayland window was supposed to be
freed using the destroy_func, as is commonly done. This was previously
broken, as the user data was just NULL:ed when exported, and only
actually destroyed when unexporting before having exported.
While e016d9a5dba6f6f99aee94d0b72c00bee299b96a fixed this, it introduced
a regression, as GtkWindow was nice enough to free the memory anyway
after having received the exported handle, causing it now to double
free.
https://bugzilla.gnome.org/show_bug.cgi?id=782109
|
| |
|
|
|
|
|
| |
Add a comment pointing to the related bug for dropdown menu
margin.
|
|
|
|
|
|
| |
This reverts commit af76e138f947d5cf3e83e4b820f7e64fd0316799.
The margin was actually related to:
https://bugzilla.gnome.org/show_bug.cgi?id=591258
|
| |
|
|
|
|
|
| |
That margin was probably a left over to workaround some placement
issue on dropdowns which doesn't exist anymore.
|
|
|
|
|
|
|
| |
The application might not have exported, and it'll be too late for it
at this point anyway, so lets be helpful and not leak it.
https://bugzilla.gnome.org/show_bug.cgi?id=782109
|
|
|
|
|
|
|
|
| |
Otherwise in GC-ed environments the `g_source_remove` call during
disposal might be called on an already removed source, which results in
unnecessary console output.
https://bugzilla.gnome.org/show_bug.cgi?id=778301
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=781214
|
|
|
|
|
|
|
| |
Don't assign the value of a variable to itself. It was added just for
clarity, but it makes coverity complain, so remove it.
https://bugzilla.gnome.org/show_bug.cgi?id=780301
|
|
|
|
|
|
|
|
| |
Use the gravity enum values when converting to gravity. It doesn't fix
anything, since the enum values were identical, but it makes a coverity
warning go away.
https://bugzilla.gnome.org/show_bug.cgi?id=780301
|
|
|
|
|
|
| |
g_content_type_from_mime_type may return NULL, deal with that.
https://bugzilla.gnome.org/show_bug.cgi?id=782180
|
|
|
|
| |
This reverts commit 251e216052cab4fd04e39c7872395b64363c11da.
|
|
|
|
|
|
|
| |
The application might not have exported, and it'll be too late for it
at this point anyway, so lets be helpful and not leak it.
https://bugzilla.gnome.org/show_bug.cgi?id=782109
|
|
|
|
|
|
|
| |
It was only cleared when unexported, but we could just as well clear it
when its used too.
https://bugzilla.gnome.org/show_bug.cgi?id=782109
|
|
|
|
|
|
|
| |
If the button is deactivated, it should not appear to be hovered
anymore.
https://bugzilla.gnome.org/show_bug.cgi?id=781992
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
5bb12474d975ee4b790c5 removed the dnd window movement code to let
the gdk backends handle the window movement instead. While this
works for X11/wayland the win32 backend still uses the unmanaged
interface and expects the window movement to be handled on the gtk
side. This restores the functionality in case the dnd is unmanaged.
This fixes the drag window on Windows being stuck in the top left
corner instead of following the drag position.
https://bugzilla.gnome.org/show_bug.cgi?id=781737
|
| |
|
| |
|
|
|
|
| |
We want the warnings, but not every single message.
|
|
|
|
|
|
|
| |
Creating with `gtk_popover_new_from_model` should be exactly the same as
if via `gtk_popover_new` plus `gtk_popover_bind_model`.
Also remove the style if the model is unbound at any point.
|
|
|
|
|
|
|
|
| |
strings returned by gtk_widget_get_tooltip_text() and
gtk_widget_get_tooltip_markup() has to be freed when no longer
required.
https://bugzilla.gnome.org/show_bug.cgi?id=782202
|
|
|
|
| |
They are unnecessary now that we have gtk_widget_measure.
|
| |
|
|
|
|
| |
We don't use adjusted_allocation after this line.
|
|
|
|
| |
It's unused.
|