AuroraMiddleware/gtk
1
0
Fork 1
mirror of https://gitlab.gnome.org/GNOME/gtk.git synced 2024-12-29 15:01:23 +00:00
Code Issues Projects Releases Wiki Activity
4e5976427b
gtk/gdk/win32/gdkcairocontext-win32.h

73 lines
2.5 KiB
C
Raw Normal View History

gdk: Add Cairo context implementations for all backends And make the GdkCairoContext as abstract. The idea of this and thje following commits is to get rid of all Cairo code in gdksurface.c (and $backend/gdksurface-$backend.c) by moving that code into the Cairo context files. In particular, the GdkSurfaceClass.begin_frame/end_frame() functions (which are currently exclusively used by the Cairo code should end up being moved to GdkDrawContextClass.begin/end_frame(). This has multiple benefits: 1. It unifies code between the different drawing contexts. GL lives in GLContext, Vulkan in VulkanContext and Cairo in CairoContext. In turn, this makes it way easier to reason about what's going on in surface-specific code. Currently pretty much all backends do things wrong when they want to sync to drawing or to the frame clock. 2. It makes the API of GdkSurface smaller. No drawing code (apart from creating the contexts) needs to remain. 3. It confines Cairo to the Drawcontext, thereby making it way more obvious when backends are still using it in situations where it may now conflict with OpenGL (like when doing the dnd failed animation or in the APIs that I'm removing in this branch). 4. We have 2 very different types of Cairo contexts: The X/win32 model, where we have a natively supported Cairo backend but do double buffering ourselves and use similar surfaces and the Wayland/Broadway model where we use image surfaces without any Cairo backend support and have to submit the buffers manually. By not sharing code between those 2 versions, we can make the actual code way smaller. We also get around the need to create 1x1 image surfaces in the Wayland backend where we pretend there's a native Cairo surface.
2018-04-12 14:48:31 +00:00
/* GDK - The GIMP Drawing Kit
*
* Copyright © 2018 Benjamin Otte
*
* This library is free software; you can redistribute it and/or
* modify it under the terms of the GNU Library General Public
* License as published by the Free Software Foundation; either
* version 2 of the License, or (at your option) any later version.
*
* This library is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
* Library General Public License for more details.
*
* You should have received a copy of the GNU Library General Public
* License along with this library. If not, see <http://www.gnu.org/licenses/>.
*/
Convert headers to #pragma once The conversion was done by guard2one.
2023-03-31 19:11:10 +00:00
#pragma once
gdk: Add Cairo context implementations for all backends And make the GdkCairoContext as abstract. The idea of this and thje following commits is to get rid of all Cairo code in gdksurface.c (and $backend/gdksurface-$backend.c) by moving that code into the Cairo context files. In particular, the GdkSurfaceClass.begin_frame/end_frame() functions (which are currently exclusively used by the Cairo code should end up being moved to GdkDrawContextClass.begin/end_frame(). This has multiple benefits: 1. It unifies code between the different drawing contexts. GL lives in GLContext, Vulkan in VulkanContext and Cairo in CairoContext. In turn, this makes it way easier to reason about what's going on in surface-specific code. Currently pretty much all backends do things wrong when they want to sync to drawing or to the frame clock. 2. It makes the API of GdkSurface smaller. No drawing code (apart from creating the contexts) needs to remain. 3. It confines Cairo to the Drawcontext, thereby making it way more obvious when backends are still using it in situations where it may now conflict with OpenGL (like when doing the dnd failed animation or in the APIs that I'm removing in this branch). 4. We have 2 very different types of Cairo contexts: The X/win32 model, where we have a natively supported Cairo backend but do double buffering ourselves and use similar surfaces and the Wayland/Broadway model where we use image surfaces without any Cairo backend support and have to submit the buffers manually. By not sharing code between those 2 versions, we can make the actual code way smaller. We also get around the need to create 1x1 image surfaces in the Wayland backend where we pretend there's a native Cairo surface.
2018-04-12 14:48:31 +00:00
#include "gdkconfig.h"
#include "gdkcairocontextprivate.h"
G_BEGIN_DECLS
#define GDK_TYPE_WIN32_CAIRO_CONTEXT (gdk_win32_cairo_context_get_type ())
#define GDK_WIN32_CAIRO_CONTEXT(obj) (G_TYPE_CHECK_INSTANCE_CAST ((obj), GDK_TYPE_WIN32_CAIRO_CONTEXT, GdkWin32CairoContext))
#define GDK_IS_WIN32_CAIRO_CONTEXT(obj) (G_TYPE_CHECK_INSTANCE_TYPE ((obj), GDK_TYPE_WIN32_CAIRO_CONTEXT))
#define GDK_WIN32_CAIRO_CONTEXT_CLASS(klass) (G_TYPE_CHECK_CLASS_CAST ((klass), GDK_TYPE_WIN32_CAIRO_CONTEXT, GdkWin32CairoContextClass))
#define GDK_IS_WIN32_CAIRO_CONTEXT_CLASS(klass) (G_TYPE_CHECK_CLASS_TYPE ((klass), GDK_TYPE_WIN32_CAIRO_CONTEXT))
#define GDK_WIN32_CAIRO_CONTEXT_GET_CLASS(obj) (G_TYPE_INSTANCE_GET_CLASS ((obj), GDK_TYPE_WIN32_CAIRO_CONTEXT, GdkWin32CairoContextClass))
typedef struct _GdkWin32CairoContext GdkWin32CairoContext;
typedef struct _GdkWin32CairoContextClass GdkWin32CairoContextClass;
struct _GdkWin32CairoContext
{
GdkCairoContext parent_instance;
GDK W32: Switch to GdkCairoContext * Remove DC refcounting (we trust GDK to always do begin_frame/end_frame calls in pairs) * Now that there's no GDK-provided double-buffer up the stack, double-buffering is implemented here (though it's disabled by default - in my tests it didn't provide any visual improvements, but did decrease performance). * For some reason delaying window resizes until the point where we need to blit the double-buffer into the window leads to visual glitches, so doulbe-buffered windows are resized in begin_frame, same as non-double-buffered ones. * New code to clear the paint region, for all drawing modes. Hopefully, it isn't duplicated anywhere up the stack. * GL has its own context now, so remove any GL-related comments. * Layered windows are still used (because cairo actually works better with them) * A bit more code re-use for layered windows * Some functions that were local to gdksurface-win32.c are made usable for the whole backend * Drag-indicator drawing is temporarily commented out to match a similar change in X11 backend
2018-04-24 15:14:23 +00:00
/* Set to TRUE when double-buffering is used.
* Layered windows use their own, custom double-buffering
* code that is unaffected by this flag.
*/
guint double_buffered : 1;
/* The a surface for double-buffering. We keep it
* around between repaints, and only re-allocate it
* if it's too small. */
cairo_surface_t *db_surface;
Replace "gint" with "int"
2020-07-24 13:54:49 +00:00
int db_width;
int db_height;
GDK W32: Switch to GdkCairoContext * Remove DC refcounting (we trust GDK to always do begin_frame/end_frame calls in pairs) * Now that there's no GDK-provided double-buffer up the stack, double-buffering is implemented here (though it's disabled by default - in my tests it didn't provide any visual improvements, but did decrease performance). * For some reason delaying window resizes until the point where we need to blit the double-buffer into the window leads to visual glitches, so doulbe-buffered windows are resized in begin_frame, same as non-double-buffered ones. * New code to clear the paint region, for all drawing modes. Hopefully, it isn't duplicated anywhere up the stack. * GL has its own context now, so remove any GL-related comments. * Layered windows are still used (because cairo actually works better with them) * A bit more code re-use for layered windows * Some functions that were local to gdksurface-win32.c are made usable for the whole backend * Drag-indicator drawing is temporarily commented out to match a similar change in X11 backend
2018-04-24 15:14:23 +00:00
GDK/Win32: Remove layered windows usage In GTK4, we are now defaulting to the OpenGL renderer with the Cairo renderer only used as a fallback, so there is no point keeping the code paths that use layered windows as layered windows do not work well with OpenGL nor Vulkan.
2020-11-05 08:24:40 +00:00
/* Surface for the window DC */
GDK W32: Switch to GdkCairoContext * Remove DC refcounting (we trust GDK to always do begin_frame/end_frame calls in pairs) * Now that there's no GDK-provided double-buffer up the stack, double-buffering is implemented here (though it's disabled by default - in my tests it didn't provide any visual improvements, but did decrease performance). * For some reason delaying window resizes until the point where we need to blit the double-buffer into the window leads to visual glitches, so doulbe-buffered windows are resized in begin_frame, same as non-double-buffered ones. * New code to clear the paint region, for all drawing modes. Hopefully, it isn't duplicated anywhere up the stack. * GL has its own context now, so remove any GL-related comments. * Layered windows are still used (because cairo actually works better with them) * A bit more code re-use for layered windows * Some functions that were local to gdksurface-win32.c are made usable for the whole backend * Drag-indicator drawing is temporarily commented out to match a similar change in X11 backend
2018-04-24 15:14:23 +00:00
cairo_surface_t *window_surface;
/* A reference to db_surface (when double-buffering).
GDK/Win32: Remove layered windows usage In GTK4, we are now defaulting to the OpenGL renderer with the Cairo renderer only used as a fallback, so there is no point keeping the code paths that use layered windows as layered windows do not work well with OpenGL nor Vulkan.
2020-11-05 08:24:40 +00:00
* When not using double-buffering this is a reference
* to window_surface.
GDK W32: Switch to GdkCairoContext * Remove DC refcounting (we trust GDK to always do begin_frame/end_frame calls in pairs) * Now that there's no GDK-provided double-buffer up the stack, double-buffering is implemented here (though it's disabled by default - in my tests it didn't provide any visual improvements, but did decrease performance). * For some reason delaying window resizes until the point where we need to blit the double-buffer into the window leads to visual glitches, so doulbe-buffered windows are resized in begin_frame, same as non-double-buffered ones. * New code to clear the paint region, for all drawing modes. Hopefully, it isn't duplicated anywhere up the stack. * GL has its own context now, so remove any GL-related comments. * Layered windows are still used (because cairo actually works better with them) * A bit more code re-use for layered windows * Some functions that were local to gdksurface-win32.c are made usable for the whole backend * Drag-indicator drawing is temporarily commented out to match a similar change in X11 backend
2018-04-24 15:14:23 +00:00
*/
cairo_surface_t *paint_surface;
gdk: Add Cairo context implementations for all backends And make the GdkCairoContext as abstract. The idea of this and thje following commits is to get rid of all Cairo code in gdksurface.c (and $backend/gdksurface-$backend.c) by moving that code into the Cairo context files. In particular, the GdkSurfaceClass.begin_frame/end_frame() functions (which are currently exclusively used by the Cairo code should end up being moved to GdkDrawContextClass.begin/end_frame(). This has multiple benefits: 1. It unifies code between the different drawing contexts. GL lives in GLContext, Vulkan in VulkanContext and Cairo in CairoContext. In turn, this makes it way easier to reason about what's going on in surface-specific code. Currently pretty much all backends do things wrong when they want to sync to drawing or to the frame clock. 2. It makes the API of GdkSurface smaller. No drawing code (apart from creating the contexts) needs to remain. 3. It confines Cairo to the Drawcontext, thereby making it way more obvious when backends are still using it in situations where it may now conflict with OpenGL (like when doing the dnd failed animation or in the APIs that I'm removing in this branch). 4. We have 2 very different types of Cairo contexts: The X/win32 model, where we have a natively supported Cairo backend but do double buffering ourselves and use similar surfaces and the Wayland/Broadway model where we use image surfaces without any Cairo backend support and have to submit the buffers manually. By not sharing code between those 2 versions, we can make the actual code way smaller. We also get around the need to create 1x1 image surfaces in the Wayland backend where we pretend there's a native Cairo surface.
2018-04-12 14:48:31 +00:00
};
struct _GdkWin32CairoContextClass
{
GdkCairoContextClass parent_class;
};
GDK_AVAILABLE_IN_ALL
GType gdk_win32_cairo_context_get_type (void) G_GNUC_CONST;
G_END_DECLS
Reference in New Issue Copy Permalink