| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\
| |
| |
| |
| |
| |
| | |
wayland: Implement minimization
Closes #2688
See merge request GNOME/gtk!2861
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Use the set_minimized method of the xdg_toplevel
interface to implement minimization as well as possible.
It is not possible, since there is no corresponding
state that we could use to update our surface state,
but in practice, it works well enough.
Fixes: #2688
|
|\ \
| | |
| | |
| | |
| | | |
macos: fix rendering artifacts with hover transitions
See merge request GNOME/gtk!2862
|
| |/
| |
| |
| |
| | |
Using an image surface seems to fix some rendering artifacts when
performing cross-fade CSS transitions.
|
|/
|
|
|
| |
Bring in line with gtk3, in terms of startup notification and
activation support.
|
|
|
|
|
| |
We need to resolve the array length manually, because g-ir-scanner
cannot turn an enumeration member into a constant size.
|
| |
|
|
|
|
|
|
| |
This commit fix the warning:
../gdk/wayland/gdkdisplay-wayland.c:1079: Warning: GdkWayland: gdk_wayland_display_set_cursor_theme: unknown parameter 'name' in documentation comment, should be 'theme'
|
|
|
|
| |
Add a few missing parameters in doc comments.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
non-debug mode
Currently GTK can be built with G_ENABLE_DEBUG which enables various debug code and parsing
of those env vars, or without, which instead of parsing them prints a warning if they are set.
While building with G_ENABLE_DEBUG isn't strictly needed it's the only way to make GTK_DEBUG=interactive work,
which is a nice thing to have always.
This enables parsing of those env vars in any case and allows specific values being marked as also
available when not built with G_ENABLE_DEBUG (interactive for example). If not built with G_ENABLE_DEBUG
then all unavailable values will be marked as such in the help output and a note is added that
GTK needs to be built with G_ENABLE_DEBUG to use them, which should help discoverability.
|
|
|
|
|
| |
We were leaking references returned from g_list_model_get_item
in some places.
|
|
|
|
|
| |
We were leaking references returned from g_list_model_get_item
in some places.
|
|
|
|
|
| |
We were leaking references returned from g_list_model_get_item
in some places.
|
|\
| |
| |
| |
| |
| |
| | |
Text handle fixes
Closes #3176
See merge request GNOME/gtk!2785
|
| |
| |
| |
| |
| | |
If a surface is hidden, then shown again, it should preserve the
input area specified. Make sure that happens.
|
| |
| |
| |
| |
| | |
We don't need to interact with GdkGLContext here to keep the
current context active.
|
| | |
|
|/
|
|
|
| |
This is better for situations where the window is decorated and therefore we can
rely on window system clipping of rounded corners.
|
|
|
|
| |
Fix argument ordering of gdk_cursor_new_from_name.
|
|\
| |
| |
| |
| | |
macos: gl context improvements and event cleanup
See merge request GNOME/gtk!2780
|
| |
| |
| |
| |
| | |
Once we figure out what is going on with textures, changes are we'll be
able to let this stay a zero rect. But that is still a bit up in the air right now.
|
| |
| |
| |
| | |
This ensures that we only copy the changed area.
|
| |
| |
| |
| |
| | |
We can use gdk_surface_request_motion() now instead of our extra
helper to do essentially the same thing.
|
| |
| |
| |
| |
| | |
This simplifies the creation by always creating the dummy views, and then
removes it if necessary by detecting the begin_frame/end_frame pair.
|
| |
| |
| |
| |
| | |
This fixes the calculation of the position of the pointer over the surface
which was incorrectly providing negative values.
|
|\ \
| |/
|/|
| |
| |
| |
| | |
[master] GdkW32: remove klassTEMPSHADOW
Closes #2019
See merge request GNOME/gtk!2750
|
| |
| |
| |
| | |
Fixes issue #2019
|
| |
| |
| |
| | |
This reverts commit 2120e9df880cabfe21d5a4e8c2d0e6804a4e09d8.
|
| |
| |
| |
| | |
Extraneous pair of parens snuck in with 2120e9df88.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When we close grabbing popups due to an outside
click, check at each level if the click is still
outside. This makes closing the nested popover
menu in the popover on page 3 of widget-factory
work as expected, when you click the menubutton
again.
|
| |
| |
| |
| |
| |
| | |
When an event happens on a non-grabbing popup that hangs off
a grabbing popup, don't trigger the autohide. This makes touch
text handles work inside the popover on page 3 of widget-factory.
|
| |
| |
| |
| |
| |
| |
| | |
Set modifier state of scroll events, so Ctrl-scroll
works.
Fixes: #2733
|
| |
| |
| |
| |
| |
| |
| | |
We can just call gdk_surface_invalidate_rect here
like we do elsewhere in gdk, and I'm a bit uncertain
about the current code that adds an empty update
region.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The Cairo implementation for the Macos backend uses a toplevel
window with full transparency and a series of NSView to create opaque
regions. This improves compositor performance because it allows the
display server to avoid costly blends.
However, we want to ensure we clip better when exposing the
transparent region so that we only expose the shadows/corners as
necessary.
|
| | |
|
|\ \
| | |
| | |
| | |
| | | |
Matthiasc/for master
See merge request GNOME/gtk!2760
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
Add more details, and refer to the GdkToplevel / GdkPopup
docs.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
Make the GdkRGBA heading less repetitive.
|
| | |
| | |
| | |
| | | |
Minor additions here and there.
|
| | |
| | |
| | |
| | | |
Minor additions here and there.
|
| | |
| | |
| | |
| | |
| | |
| | | |
This typedef was not used in any public APIs, and is
only used in the MacOS backend. It is not worth preserving
as public API, move it to the only user.
|
| | |
| | |
| | |
| | |
| | | |
We no longer have a Quartz backend, it is called
MacOS now.
|
| | |
| | |
| | |
| | | |
Its MacOS now.
|
| | |
| | |
| | |
| | | |
Whitespace fix.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This implements the basics for a GdkGLContext on macOS. Currently, rendering
only is fully working for the GskCairoRenderer case where we read back pixels
into a cairo surface for rendering. More work on synchronization is required for
the GL on GskGLRenderer case.
When we attempt to render a surface itself with GL, the context will ensure that
the new GdkMacosGLView is placed within the NSWindow. In other cases, we
use a dummy NSView and NSWindow for backing the NSOpenGLContext to
ensure that we can get accelerated drawing.
This gets GtkGLArea working when running with GSK_RENDERER=cairo.
|