summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* wayland: Don't emit signals if nothing changedim-wayland-resetMatthias Clasen2018-03-261-0/+3
| | | | | We were emitting a preedit-changed even if the preedit text did not actually change, causing text views to scroll.
* snapshot: Generate better names for offset nodesBenjamin Otte2018-03-261-14/+4
|
* rendernode: Fix serializingBenjamin Otte2018-03-262-4/+5
| | | | | | | | Adding the offset node broke serialization in 2 ways: 1. We store the enum value in the node, so make sure to not change it for existing values 2. The offset node was missing in the deserialization lookup table
* iconhelper: Apply scale to paintableBenjamin Otte2018-03-261-29/+10
| | | | | | Instead of fiddling around with scale in the iconhelper (and getting it wrong), create a GtkScaler around the paintable that takes care of the scaling.
* dnd: Remove gtk_drag_set_icon_surface()Benjamin Otte2018-03-263-40/+0
| | | | All users are gone. Use gtk_drag_set_icon_paintable() instead.
* tests: Don't use gtk_drag_set_icon_surface()Benjamin Otte2018-03-261-7/+11
|
* textview: Port dnd icon to be a GdkPaintableBenjamin Otte2018-03-263-18/+20
|
* colorswatch: Port drag icon to paintablesBenjamin Otte2018-03-261-11/+9
|
* colorbutton: Port dnd icon to paintableBenjamin Otte2018-03-261-13/+12
| | | | Patch is untested, because colorbuttons can't do DND at the moment.
* treeview: Turn drag icon into paintableBenjamin Otte2018-03-262-35/+29
|
* iconview: Port DND icons to snapshot paintablesBenjamin Otte2018-03-262-36/+16
|
* tests: Remove references to long-deleted propertyBenjamin Otte2018-03-262-8/+1
|
* textutil: Make gtk_text_util_create_drag_icon() return a paintableBenjamin Otte2018-03-264-42/+31
|
* snapshot: Add gtk_snapshot_to_paintable()Benjamin Otte2018-03-266-0/+234
| | | | This is intended for DND icons
* snapshot: Export gtk_snapshot_append_layout()Benjamin Otte2018-03-265-14/+43
| | | | | | | This is the equivalent snapshot function to pango_cairo_show_layout(). Not to be confused with gtk_snapshot_render_layout(), which is the equivalent to gtk_render_layout().
* snapshot: Make gtk_snapshot_append_node() take care of offsetBenjamin Otte2018-03-267-48/+140
| | | | Push an offset node when append_node is called. That resets the offset.
* rendernode: Add an offset nodeBenjamin Otte2018-03-268-2/+226
| | | | | | | | | This is a special case of the transform node that does a 2D translation. The implementation in the Vulkan and GL renderers is crude and just does the same as the transform node. Nothing uses that node yet.
* Update Polish translationPiotr Drąg2018-03-262-443/+630
|
* colorscale: Draw gradient using render nodesBenjamin Otte2018-03-261-9/+21
| | | | Don't use Cairo when it's not needed.
* colorscale: Draw hue background as a textureBenjamin Otte2018-03-261-34/+38
| | | | No need to use Cairo here.
* colorplane: Create background image as a textureBenjamin Otte2018-03-261-48/+40
| | | | Don't create it using Cairo.
* Merge branch 'bz773274' into 'master'Matthias Clasen2018-03-251-1/+1
|\ | | | | | | | | wayland: Don't paint if the window is unmapped See merge request GNOME/gtk!32
| * wayland: Drop cairo surfaces when withdrawingOlivier Fourdan2018-03-201-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If a surface is unmapped by the client while gdk is processing updates, (for example Firefox un-mapping its window on Expose events), the windowing backend resources might be lost (for example with Wayland) which can cause a crash in end_paint(). Make sure we drop the cairo surfaces as well when hiding the surface, that will avoid the crash in gdk_surface_impl_wayland_end_paint() when trying to attach the staging cairo surface to a released wl_surface, these will be recreated when needed when the surface becomes visible again and there is no need to keep such buffers around for a surface which is not visible anyway. https://bugzilla.gnome.org/show_bug.cgi?id=793062
* | colorscale: Don't free surface data before surfaceBenjamin Otte2018-03-251-7/+6
| | | | | | | | | | | | | | When drawing onto a recording surface, source surfaces get cached. But if we g_free() the surface data after we're done, that cache is gonna point at invalid data...
* | GdkGLContext: Add a GL debug message callbackTimm Bäder2018-03-251-0/+106
| | | | | | | | | | | | | | If G_ENABLE_CONSISTENCY_CHECKS is defined (i.e. if our buildtype is 'debug'), add a opengl debug callback that prints all debug messages with a severity higher than SEVERITY_NOTIFICATION as a warning to the console.
* | gl renderer: Skip all 0-sized nodesTimm Bäder2018-03-251-0/+5
| | | | | | | | These will cause problems later on.
* | gl renderer: Remove cairo node special caseTimm Bäder2018-03-251-36/+1
| |
* | ci: Remove --werrorEmmanuele Bassi2018-03-251-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | Turns out that GCC errors out when building the GLib test suite, as it now checks for overflows in allocator functions, and we're testing for those. This would not be an issue for GTK, but since we're building GLib as a subproject, we get failures for those as well. Until we can find out how to disable errors for subprojects, or fix the GLib test suite not to trip up warnings in GCC, we're going to live without compiler warnings treated as errors for a while.
* | ci: Use the appropriate argument for errorsEmmanuele Bassi2018-03-251-1/+1
| | | | | | The option to enable fatal warnings in Meson is `--werror`.
* | Menu: Don't leak priv->motion_controllerDaniel Boles2018-03-241-0/+1
| |
* | ci: build with -WerrorBenjamin Otte2018-03-241-0/+1
| |
* | ci: Disable ccacheEmmanuele Bassi2018-03-241-3/+1
| | | | | | | | Forcibly remove any ccache use, even if it's installed.
* | docs: Style fixes for the contribution guidelinesEmmanuele Bassi2018-03-241-8/+8
| |
* | snapshot: Remove rendererBenjamin Otte2018-03-2410-38/+11
| | | | | | | | | | Now that there's no longer a need to keep the renderer around for Cairo rendering, don't do that then.
* | rendernode: Remove renderer argumentBenjamin Otte2018-03-244-27/+6
| | | | | | | | It's not needed to create Cairo nodes anymore.
* | rendernode: Create Cairo surfaces as recording surfacesBenjamin Otte2018-03-241-34/+38
| | | | | | | | | | | | | | | | | | | | This way, we can postpone the actual rendeing of the node until the renderer. This allows the renderer to choose the right scale to render at, so it can decide to use 2x scale for hidpi on its own. Last but not least, it makes all nodes independent of the context they are created in, because they do not need to know at snapshot time what they will ultimately be rendered into.
* | vulkan: Remove special case for Cairo surfacesBenjamin Otte2018-03-241-39/+9
| | | | | | | | | | This is in preparation for the next commits which switch Cairo nodes to recording surfaces.
* | Merge branch 'lrn/bug-773299' into 'master'LRN2018-03-242-24/+32
|\ \ | | | | | | | | | | | | bug 773299 2nd See merge request GNOME/gtk!79
| * | GDK W32: Adapt DnD event putting to recent changeslrn/bug-773299Руслан Ижбулатов2018-03-242-24/+32
| | | | | | | | | | | | | | | | | | | | | | | | Set the display for each event that we put. Also reorganize the dnd_event_put() function a bit, giving it a surface directly instead of setting it by implication. https://bugzilla.gnome.org/show_bug.cgi?id=773299
* | | Merge branch 'lrn/bug-773299' into 'master'LRN2018-03-245-29/+17
|\ \ \ | |/ / | | | | | | | | | bug 773299 See merge request GNOME/gtk!78
| * | GDK W32: Don't check dest_surface for != NULL on button eventsРуслан Ижбулатов2018-03-241-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | dest_surface is going to always be NULL for source contexts. Previously we used to put the root window there to pass this check, but root windows are gone (and root surfaces never existed to begin with), so we have to adapt. https://bugzilla.gnome.org/show_bug.cgi?id=773299
| * | GDK W32: Init display scale to the global Windows scale, not 1Руслан Ижбулатов2018-03-241-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This affects gdk_device_query_state() for the virtual device. It has no window, and is forced to query the display itself, and display defaults its scale to 1 even for HiDPI desktops. Use the same "query scale of a NULL monitor" trick that we use in other places to get the global desktop scale. https://bugzilla.gnome.org/show_bug.cgi?id=773299
| * | GDK W32: adapt to the recent changes in GdkEventРуслан Ижбулатов2018-03-243-26/+15
|/ / | | | | | | https://bugzilla.gnome.org/show_bug.cgi?id=773299
* | Update zh_CN po and po-properties translationsDz Chen2018-03-232-1406/+1547
| |
* | Adwaita: Regenerate CSS from SASSDaniel Boles2018-03-222-2/+12
| | | | | | | | | | | | | | https://gitlab.gnome.org/GNOME/gtk/merge_requests/66 introduced spurious red/green fore/background. Also, the GtkVideo stuff didn't get regenerated in.
* | Merge branch 'toolbar-spacing-fix' into 'master'Daniel Boles2018-03-223-7/+6
|\ \ | | | | | | | | | | | | theme: Be more selective when adding margins to toolbar items See merge request GNOME/gtk!66
| * | theme: Be more selective when adding margins to toolbar itemsNikita Churaev2018-03-183-7/+6
| | | | | | | | | | | | | | | Only add margins to direct children of toolbar items, this fixes the gaps between linked buttons inside custom toolbar items.
* | | surface: Make process_updates no longer be a vfuncBenjamin Otte2018-03-214-22/+4
| | |
* | | surface: Remove some unused vfuncsBenjamin Otte2018-03-211-2/+0
| | |
* | | gdk: Remove GdkSurfaceImpl::shape_combine_region vfuncBenjamin Otte2018-03-216-136/+17
| | | | | | | | | | | | | | | | | | ... and all the implementations. Input shapes still exist.