5 Commits

Author	SHA1	Message	Date
Emmanuele Bassi	def700739d	Use a single compilation symbol ... We use a compilation symbol in our build to allow the inclusion of specific headers while building GTK, to avoid the need to include only the global header. Each namespace has its own compilation symbol because we used to have different libraries, and strict symbol visibility between libraries; now that we have a single library, and we can use private symbols across namespaces while building GTK, we should have a single compilation symbol, and simplify the build rules.	2019-11-27 13:33:43 +00:00
Andy Holmes	907a86fd93	Correct Gdk backend import paths and related gtk-doc ... Correct the paths in the include guard warnings and use the `@Include` directive for the Gdk backends.	2019-11-18 00:31:38 -08:00
Matthias Clasen	4c150d8eb5	The big versioning cleanup ... Remove all the old 2.x and 3.x version annotations. GTK+ 4 is a new start, and from the perspective of a GTK+ 4 developer all these APIs have been around since the beginning.	2018-02-06 01:16:32 -05:00
Daniel Boles	406db15066	gdk/gtk: Fix more AVAILABLE_IN annotations to 3_92	2017-05-28 14:20:19 +01:00
Tom Schoonjans	758d26738a	quartz: add support for Gtk+4 ... The addition of GdkMonitor broke the quartz backend. This patch restores that support by adding a new class GdkQuartzMonitor, and by modifying the existing classes GdkQuartzDisplay and GdkQuartzScreen where necessary. It should be noted that this patch is essentially a refactor as no new functionality that will impact the user has been added or removed. https://bugzilla.gnome.org/show_bug.cgi?id=779184	2017-04-01 16:45:37 -04:00