| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | |
|
| |
|
|
| |
Unused.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
gtk_widget_reparent is gone so we don't need this anymore.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Leftovers from when it was still using a GtkArrow
|
| |
|
|
| |
We don't create a box anymore here.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
xdg_shell v6 allows grabless popups, whose behavior is not that
different from override redirect windows with no grab to take
keyboard input (and pointer events outside).
This means we can relax the requirement to have a grab before
creating an xdg_popup. The warning is still useful to have so
people stop relying on gdk_window_show();gdk_device_grab() being
an ok pattern to popup a window, it's been moved to wayland
implementation of gdk_device_grab() instead, so we warn if trying
to grab a GDK_WINDOW_TEMP window that's already visible.
https://bugzilla.gnome.org/show_bug.cgi?id=771694
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Newer versions of Automake warn about forward compatibility when the
build uses sources in sub-directories without the subdir-objects option.
Both GTK+ and GDK have an almost-but-not-quite non-recursive Automake
layout, with sources in sub-directories contributing to the build of a
top-level object.
In theory, just adding subdir-objects to AM_INIT_AUTOMAKE would be
enough, but the test suite references sources in a different top-level
in order to build tests that verify the implementation of private data
structures. This is not really allowed when using subdir-objects and out
of srcdir builds. In order to fix this case, we require some ad hoc
rules to create symbolic links in the appropriate build directory.
|
| |
|
|
|
|
|
| |
the darker bottom border used on buttons looks bad on circular ones
so now a gradient clipped on the border-box and a transparent
border is used in that partcular case.
See https://bugzilla.gnome.org/show_bug.cgi?id=771205 for details.
|
| |
|
|
|
|
| |
$button_fill contains the background-image property value of
buttons, having it readable outside the drawing mixin allows, for
example, stacking background images in an easier way.
|
| |
|
|
| |
aggregate circular button style to the main button structure.
|
| |
|
|
|
| |
...in place of the circular-button one, killing the custom style
shipped, realying on the theme style.
|
| |
|
|
| |
The foreigndrawing test has been removed.
|
| |
|
|
|
| |
No need to use an internal function, and no need to store the icon size
id, since we're using the id as the offset.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This updates all the projects files to be be named appropriately as we move from GTK-3.x to 4.x,
and updates the autotools files so that things are distributed and generated properly.
Also remove deprecated/gtkstatusicon-quartz.c from gtk/Makefile.am, as that was causing 'make dist'
to fail as that file has been removed.
This fixes 'make dist' with the updated existing project files in proper order.
Note that this does not include the new GSK, which will be added later, so the project files do
not yet build the whole stack on Visual Studio at this point.
|
| |
|
|
| |
We dropped it...
|
| |
|
|
|
|
|
|
|
|
|
| |
Make the Makefile.am targets for generating the Visual Studio projects re-generate the
project files and the header listings whenever the Makefile.am's that include
build/Makefile.msvcproj changes, so that whenever a source/header is added, they will
be reflected in the projects and in the property sheets that are used to copy the
headers.
Also ensure that these are applied to the vs11, vs12 and vs14 projects when this
happens, as they are copied and processed from the Visual Studio 2010 projects.
|
| | |
|
| |
|
|
|
| |
Remove information that is only relevant for porting to GTK+ 3,
and put scaffolding in place for information relevant to GTK+ 4.
|
| |
|
|
| |
When disposing the GskRenderer.
|
| |
|
|
| |
We need to destroy the node's surface when finalizing it.
|
| | |
|
| |
|
|
|
|
| |
We need to only parse the public sources during the introspection step,
otherwise the introspection scanner will try to access private data
types.
|
| |
|
|
| |
We can use the LDFLAGS target build.
|
| |
|
|
| |
This is just easier to avoid parallel installation problems.
|
| |
|
|
|
| |
Instead of gtk-query-immodules-4.0, lets call it gtk4-query-immodules,
to use the same prefix as all the other versioned binaries.
|
| |
|
|
| |
This makes gtk-doc produce output again.
|
| | |
|
| |
|
|
| |
In addition to d22e5e69d93401f8f0a040767fbf69ac5643a19d
|
| |
|
|
| |
GSK is part of the 4.0 development cycle.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
While porting GTK to GskRenderer we noticed that the current fallback
code for widgets using Cairo to draw is not enough to cover all the
possible cases.
For instance, if a container widget still uses GtkWidget::draw to render
its children, and at least one of them has been ported to using render
nodes instead, the container won't know how to draw it.
For this reason we want to provide to layers above GSK the ability to
create a "fallback" renderer instance, created using a "parent"
GskRenderer instance, but using a Cairo context as the rendering target
instead of a GdkDrawingContext.
GTK will use this inside the gtk_widget_draw() implementation, if a
widget implements GtkWidgetClass.get_render_node().
|
| |
|
|
|
| |
The Cairo renderer has been lagging behind a series of changes inside
GskRenderer, like surface-less nodes, so it needs to be updated.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We're going to need to allow rendering on a specific cairo_t in order to
implement fallback code paths inside GTK; this means that there will be
times when we have a transient GskRenderer instance that does not have a
GdkDrawingContext to draw on.
Instead of adding a new render() implementation for those cases and then
decide which one to use, we can remove the drawing context argument from
the virtual function itself, and allow using a NULL GdkDrawingContext
when calling gsk_renderer_render(). A later commit will add a generic
function to create a transient GskRenderer with a cairo_t attached to
it.
Renderers inside GSK will have to check whether we have access to a
GdkDrawingContext, in which case we're going to use it; or if we have
access to a cairo_t and a window.
|
| | |
|
| |
|
|
|
|
|
| |
GskRenderNode is, at its core, a write-only API; you're supposed to set
up the render nodes instead of querying them for state.
Querying render nodes is left to the GskRenderer implementation.
|
| |
|
|
|
| |
We control the clearing inside each GskRenderer implementation, and we
don't allow providing a target surface any more.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Warning! This breaks GtkAccelLabel. It will be fixed in the next
commit.
|
| | |
|
| |
|
|
|
|
|
|
| |
Add a should_propagate function for render nodes. Eventually,
this is meant to avoid creating render nodes for child widgets
that are outside the parents clip area. Since we don't have
that information available right now, just filter out nondrawable
children for now.
|
