| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
Needed since 049cbc8b74aa7a6fff1627c8c65cbfd3c86dfde8
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch introduces support for using the newly introduced
monitor objects in the XRandR protocol. These objects are meant
to be used to denote a set of rectangles representing a logical
monitor, and are used to hide details like monitor tiling and
virtual gpu outputs.
This uses the new objects instead of crtc/outputs objects when
they are available to create the monitor lists. X server 1.18
is required on the server side for randr 1.5.
https://bugzilla.gnome.org/show_bug.cgi?id=749561
|
|
|
|
|
|
|
| |
It's now needed by gtk-launch, so it's just the case to enable it for all the
builds except the win32 one, instead of adding it for every unix backend.
https://bugzilla.gnome.org/show_bug.cgi?id=744086
|
|
|
|
|
|
|
| |
This reverts commit 57751fa391fce8b9f208c41260e8968dd4cdc800.
I've been told that this is not, in fact, a pkg-config bug,
but a pkg-config feature.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Requires Vista and newer.
* Create surfaces with cairo_win32_surface_create_with_format
* Provide an rgba visual that can be distinguished from the system visual
* Make rgba visual the best available visual
* Enable alpha-transparency for all windows that we control
* Check for appropriate cairo capabilities at configure time
(W32 - 1.14.3 newer than 2015-04-14; others - 1.14.0)
* Check for composition support before enabling CSDs
* Re-enable transparency on WM_DWMCOMPOSITIONCHANGED
Windows that were created while composition was enabled and that were CSDed
as a result and will look ugly (thick black borders or no borders at all) once
composition is disabled.
If composition is enabled afterwards, they will return back to normal.
This happens, for example, when RDP session is opened to a desktop where a GTK
application is running. For W7/Vista windows will only re-gain transparency after
the RDP session is closed. For W8 transparency will only be gone momentarily.
Windows that were created while composition was disabled will not be CSDed
automatically and will use SSD (WM decorations), while windows that are CSDed
manually will get a thin square border.
If composition is enabled afterwards, these windows will not change.
This is most noticeable for system menus (popup menus are often generated
on the fly, system menus are created once) and some dialogues (About dialogue,
for example).
https://bugzilla.gnome.org/show_bug.cgi?id=727316
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
isatty() on MSYS2 returns non-zero if the fd is stdout and is redirected
to /dev/null. That lets xgettext to produce colorized output and leads
to an assertion failure during terminal type detection.
Although the problem should be fixed in MSYS2, isatty() could behave
wrongly in many ways on Windows. Since gtk+ doesn't need colorized
output, it would be safer to bypass the terminal dependent code.
See also:
https://lists.gnu.org/archive/html/bug-gettext/2015-04/msg00004.html
https://bugzilla.gnome.org/show_bug.cgi?id=748346
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The current GdkScreen->is_composited() is a stub as we were having Windows
XP being supported, which does not support Desktop Window Manager (DWM),
which is used by Windows for composition.
Windows Vista and later support DWM, and it is always enabled on Windows 8/
Server 2012 and later.
Please note that as we are dropping XP support in this cycle, this is the
commit that would say goodbye to Windows XP support for GTK+-3.x, by
linking directly to dwmapi.dll. This means, we only check whether we are
on Windows 8 or Server 2012 (or later) to see whether we unconditionally
have composition enabled.
https://bugzilla.gnome.org/show_bug.cgi?id=741849
|
| |
|
|
|
|
|
|
|
| |
Make it possible to control libcanberra support so we don't risk ending up with
a cyclic dependency when using packages: gtk+ -> libcanberra-gtk3 -> gtk+
https://bugzilla.gnome.org/show_bug.cgi?id=746904
|
|
|
|
| |
Bump the version to 3.17.0 and add version macros.
|
| |
|
| |
|
|
|
|
|
|
|
| |
Using AC_CHECK_TYPE instead of AC_TRY_COMPILE avoids compiler
warnings from -Werror.
https://bugzilla.gnome.org/show_bug.cgi?id=535929
|
|
|
|
|
|
| |
It apparently doesn't exist everywhere.
https://bugzilla.gnome.org/show_bug.cgi?id=745578
|
| |
|
|
|
|
| |
The new xgettext check was leaving a messages.po file behind.
|
|
|
|
| |
Check that xgettext understands glade files.
|
|
|
|
| |
It is no longer needed.
|
| |
|
| |
|
|
|
|
| |
So apps can require 3.15.7 for new api.
|
| |
|
|
|
|
| |
Needed for g_autoptr.
|
| |
|
|
|
|
|
| |
We need the bump in order to allow projects to depend on newly added
API.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
We are using epoxy api in GtkGLArea, so we need to link against it.
https://bugzilla.gnome.org/show_bug.cgi?id=740162
|
|
|
|
| |
Having this in the source seems more appropriate.
|
|
|
|
|
| |
We already juggle the print backends here, might as well
produce the list.
|
|
|
|
|
|
| |
gtk-update-icon-cache is no longer used at build time, so a lot
of the complicated machinery we have around that (conditional
build, cross build, etc) are no longer required.
|
| |
|
| |
|
| |
|
|
|
|
| |
Recent changes to the Mir backend require an unreleased version.
|
|
|
|
| |
This is needed for cairo_set_device_scale()
|
|
|
|
| |
Needed for ATK_STATE_HAS_TOOLTIP.
|
| |
|
| |
|
|
|
|
|
|
| |
This is disabled by default. Enable with --enable-mir-backend.
This backend is a combined work of Robert Ancell and Ryan Lortie.
|
|
|
|
| |
For extra fun, make some noise.
|
|
|
|
|
|
|
| |
It doesn't report -I${prefix}/include in cflags, even if .pc
files explicitly put it there. This was breaking the build
outside of a jhbuild shell when libepoxy is in the jhbuild tree
but not in /usr.
|
|
|
|
| |
This uses EGL to implement GdkGLContext for wayland.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If we want to use OpenGL in GDK then we have two choices; either:
- find the GL headers on each platform
- do extension discovery
- implement all the crazy dlopen()/dlsym() dispatch tables
*or* use libepoxy, which shields us from all this madness and provides a
decent layer for GL clients to use, without creating its own namespace.
Epoxy is also used by other projects, like Xorg and piglit, and it's
portable to all the platforms GDK cares about.
https://bugzilla.gnome.org/show_bug.cgi?id=119189
|
| |
|