GitLab

g_logv adds one for us already.

This is showing up in bug reports like
https://bugzilla.gnome.org/show_bug.cgi?id=762754
so better add a note that gives a hint at the solution.

Setting label-yalign should affect the border gadget, but we need to
compensate for its position by moving the child down or up, depending on
the border gadget's position, so the child never moves.

https://bugzilla.gnome.org/show_bug.cgi?id=762123

The gdkprivate-wayland.h header file is included from the top-level gdk
directory; this means that all included files referenced in the header
must be relative to the `gdk` directory, otherwise the build will fail
when the build directory is not equal to the source directory.

This commit fixes a build failure under continuous:

In file included from ../../gdk/gdkdisplaymanager.c:60:0:
../../gdk/wayland/gdkprivate-wayland.h:40:51: fatal error:
gtk-primary-selection-client-protocol.h: No such file or directory
 #include "gtk-primary-selection-client-protocol.h"
                                                   ^
compilation terminated.
Makefile:1155: recipe for target 'libgdk_3_la-gdkdisplaymanager.lo' failed
make[4]: *** [libgdk_3_la-gdkdisplaymanager.lo] Error 1

This allows us to make more initialization methods private to the
screen object.

It can be called during the screen object initilization

Just reorder code in preparation to calling functions defined
before this one

Except for the init function, all the visual related code is made
of gdkscreen vfuncs, so let's move it to gdkscreen-win32. This way
we avoid keeping other static variables and instead store the info
inside the screen struct.

Strip unneeded IDs.

No need to cram it in the same file as the main window.

Add some padding on the right, to avoid the scrollbar and make
the sidebar appear balanced.

It is no longer necessary to add extra margins around the
center child in a headerbar.

The sliding is a little disorienting, so turn it off by default
and add a checkbutton for it in the gear menu.

It just looks wrong if the file chooser comes up with
"Other Locations" ellipsized. Treat it like the other
fixed entries. We only want to ellipsize bookmarks, because
their length is unpredictable.

Clean up any deprecation warnings from the css examples in
gtk3-demo.

The special case is coded into Wine, but it makes notebooks
disappear wrong. So remove it.

This is naive code in that it doesn't do the rounded edges for the
tab items yet. We can fix that later I guess.

We now draw real Windows 95 buttons.

Also split out a draw_edge() function that is supposed to emulate
Windows' DrawEdge() function. I guess we'll need it in other places,
too.

This gets rid of the decompose_mask utility entirely and simplifies
backend code.

Removes duplicated code and makes sure we use the version which
is safe against infinite loops

So far, this only reworks the tabs at top implementation.
Windows doesn't have support for theming tabs at left/right/bottom
so we need to figure out what to do there. Wine falls back to
unthemed code.

This is necessary for GtkNotebook so that the stack is always drawn
before the header.
And that is necessary so that the active tab can use negative
margins to overdraw the border of the stack to create a gap and
simulate old GTK2-style visuals for notebooks.

Caveat: over() and margins() arent' printed, but they are soon gonna
be removed anyway.

This is relevant for the Windows theme, which is the only theme that
uses padding on decorations. All other themes are unaffected.

:active is reserved for "mouse button down on node", so we have to use
something else. And stack switcher and radio buttons use :checked for
the active widget, so it makes sense to use :checked for the active tab,
too.

Themes have been adapted.

TODO: Implement :active for tabs.

Fixes black areas in source view of gtk-demo.

I am testing GTK+ master against mutter 3.19.90, so I'd
like GTK+ to survive even when the compositor does not
support the primary selection interface.

When the offset gets smaller than min_offset, we can't
access the array at that position.

Parsing <action-widgets> could sometimes fail to free
some of the data, if a nonexisting widget is referenced.
Found by gcc's leak sanitizer.