GTK is a multi-platform toolkit for creating graphical user interfaces.
Go to file
Руслан Ижбулатов 6c29e81051 W32: Massive W32 DnD fix
Massive changes to OLE2 DnD protocol, which was completely broken before:
* Keep GdkDragContext and OLE2 objects separate (don't ref/unref them
  together, don't necessarily create them together).
* Keep IDataObject formats in the object itself, not in a global variable.
* Fix getdata() to look up the request target in its format list, not in the
  global hash table
* Create target GdkDragContext on each drag_enter, destroy it on drag_leave,
  whereas IDropTarget is created when a window becomes a drag destination
  and is re-used indefinitely.
* Query the source IDataObject for its supported types, cache them in the
  target (!) context. This is how GTK+ works, honestly.
* Remember current_src_object when we initiate a drag, to be able
  to detect later on that the data object is ours and use a
  shortcut when querying targets
* Make sure GDK_DRAG_MOTION is only sent when something changes
* Support GTK drag cursors
* Ensure that exotic GTK clipboard formats are registered
  (but try to avoid registering formats that can't be used between applications).
* Don't enumerate internal formats
* Ensure that DnD indicator window can't accept drags or receive any kind of input
  (use WS_EX_TRANSPARENT).
* Remove unneeded indentation in _gdk_win32_dnd_do_dragdrop()
* Fix indentation in gdk_win32_drag_context_drop_finish()
* Remove obsolete comments in _gdk_win32_window_register_dnd()
* Check for DnD in progress when processing WM_KILLFOCUS, don't emit a grab
  break event in such cases (this allows alt-tabbing while DnD is in progress,
  though there may be lingering issues with focus after dropping...)
* Support Shell ID List -> text/uri-list conversion, now it's possible
  to drop files (dragged from Explorer) on GTK+ applications
* Explicitly use RegisterClipboardFormatA() when we know that the string
  is not in unicode. Otherwise explicitly use RegisterClipboardFormatW()
  with a UTF8->UTF16 converted string
* Fix _gdk_win32_display_get_selection_owner() to correctly bail
  when selection owner HWND is NULL (looking up GdkWindow for NULL
  HWND always succeeds and returns the root window - not the intended
  effect)
* More logging
* Send DROP_FINISHED event after DnD loop ends
* Send STATUS event on feedback
* Move GetKeyboardState() and related code into _gdk_win32_window_drag_begin(),
  so that it's closer to the point where last_pt and start_pt are set
* Use & 0x80 to check for the key being pressed. Windows will set low-order bit
  to 1 for all mouse buttons to indicate that they are toggled, so simply
  checking for the value not being 0 is not enough anymore.
  This is probably a new thing in modern W32 that didn't exist before
  (OLE2 DnD code is old).
* Fixed (hopefully) and simplified HiDPI parts of the code.

Also adds managed DnD implementation for W32 GDK backend (for both
OLE2 and LOCAL protocols). Mostly a copy of the X11 backend code, but
there are some minor differences:
* doesn't use drag_window field in GdkDragContext,
  uses the one in GdkWin32DragContext exclusively
* subtracts hotspot offset from the window coordinates when showing
  the dragback animation
* tries to consistently support scaling and caches the scale
  in the context
* Some keynav code is removed (places where grabbing/ungrabbing should
  happen is marked with TODOs), and the rest is probably inert.

Also significantly changes the way selection (and clipboard) is handled
(as MSDN rightly notes, the handling for DnD and Clipboard
 formats is virtually the same, so it makes sense to handle
 both with the same code):
* Don't spam GDK_OWNER_CHANGE, send them only when owner
  actually changes
* Open clipboard when our process becomes the clipboard owner
  (we are doing it anyway, to empty the clipboard and *become* the owner),
  and then don't close it until a scheduled selection request event
  (with TARGETS target) is received. Process that event by announcing
  all of our supported formats (by that time add_targets() should have
  been called up the stack, thus the formats are known; just in case,
  add_targets() will also schedule a selection request, if one isn't
  scheduled already, so that late-coming formats can still be announced).
* Allow clipboard opening for selection_convert() to be delayed if it
  fails initially.
* The last two points above should fix all the bugs about GTK+ rising
  too much ruckus over OpenClipboard() failures, as owner change
  *is allowed* to fail (though not all callers currently handle
  that case), and selection_convert() is asynchronous to begin with.
  Still, this is somewhat risky, as there's a possibility that the
  code will work in unexpected ways and the clipboard will remain open.
  There's now logging to track the clipboard being opened and closed,
  and a number of failsafes that try to ensure that it isn't kept open
  for no reason.
* Added copious notes on the way clipboard works on X11, Windows and GDK-W32,
  also removed old comments in DnD implementation, replaced some of them
  with the new ones
* A lot of crufty module-global variables are stuffed into a singleton
  object, GdkWin32Selection. It's technically possible to make it a
  sub-object of the Display object (the way Wayland backend does),
  but since Display object on W32 is a singleton anyway... why bother?
* Fixed the send_change_events() a bit (was slightly broken in one of the
  previous iterations)
* Ensure that there's no confusion between selection conversion (an artifact
  term from X11) and selection transmutation (changing the data to be W32-compatible)
* Put all the transmutation code and format-target-matching code into gdkselection-win32.c,
  now this code isn't spread across multiple files.
* Consequently, moved some code away from gdkproperty-win32.c and gdkdnd-win32.c
* Extensive format transmutation checks for OLE2 DnD and clipboard.
  We now keep track of which format mappings are for transmutations,
  and which aren't (for example, when formats are passed as-is, or when
  a registered name is just an alias)
* Put transmutation code into separate functions

* Ensure that drop target keeps a format->target map for supported formats,
  this is useful when selection_convert() is called, as it only receives a
  single target and no hints on the format from which the data should
  be transmuted into this target.
* Add clear_targets() on W32, to de called by GTK
* Use g_set_object() instead of g_ref_object() where it is allowed.
* Fix indentation (and convert tabs to spaces), remove unused variables

(This commit is cherry-picked from the gtk-3-22 branch)

https://bugzilla.gnome.org/show_bug.cgi?id=786509
2017-12-02 10:38:34 +00:00
build-aux/meson build: Fix post-install script 2017-08-14 22:31:13 +01:00
demos Finish conversion of pixbuf cell renderer icon size 2017-12-01 10:36:17 -05:00
docs GDK: Make sure W32 backend compiles without GdkDeviceManager 2017-12-02 10:37:23 +00:00
examples enums: Change GtkIconSize values 2017-11-15 14:22:17 -05:00
gdk W32: Massive W32 DnD fix 2017-12-02 10:38:34 +00:00
gsk GskVulkanGlyphCache: Remove unused struct member 2017-12-01 07:30:25 +01:00
gtk W32: Massive W32 DnD fix 2017-12-02 10:38:34 +00:00
modules gtkimcontextime.c: Fix call to gtk_style_context_get() 2017-11-21 14:16:06 +08:00
po Update POTFILES.in 2017-11-30 16:10:50 +01:00
po-properties Update POTFILES.in 2017-11-30 16:10:50 +01:00
subprojects build: Add dependency fallbacks for libs with meson ports 2017-09-12 00:24:58 +05:30
tests textview: Remove serialization API 2017-11-29 23:03:33 -05:00
testsuite textview: Replace pixbufs by textures 2017-11-29 23:22:13 -05:00
AUTHORS
config.h.meson gtkplacessidebar: implement libcloudproviders support 2017-09-04 11:32:03 -04:00
CONTRIBUTING.md Rename 'HACKING' to 'CONTRIBUTING' 2017-08-14 22:23:09 +01:00
COPYING
gtk+-4.0.pc.in gtk+-4.0.pc: Make sure to add requirements for Gsk (e.g. graphene-1.0) 2016-10-27 08:21:13 +02:00
gtk+-unix-print-4.0.pc.in Rename pc files from 3.0 to 4.0 2016-10-07 10:34:50 -04:00
gtk+.doap doap category core 2014-07-30 15:53:33 +02:00
make-pot make-pot: Make it executable 2017-08-15 16:30:14 +02:00
meson_options.txt Add an install-tests option 2017-10-10 00:14:48 -04:00
meson.build gtkplacessidebar: Adapt to libcloudproviders 0.2.x 2017-11-13 16:55:10 +01:00
NEWS 3.92.1 2017-10-18 23:17:27 +02:00
NEWS.pre-1-0
README.commits
README.md docs: Update references to Meson CLI utilities 2017-08-15 14:08:57 +01:00

GTK+ — The GTK toolkit

General information

GTK+ is a multi-platform toolkit for creating graphical user interfaces. Offering a complete set of widgets, GTK+ is suitable for projects ranging from small one-off projects to complete application suites.

GTK+ is free software and part of the GNU Project. However, the licensing terms for GTK+, the GNU LGPL, allow it to be used by all developers, including those developing proprietary software, without any license fees or royalties.

The official download location

The official web site

The official developers blog

Information about mailing lists can be found at

Building and installing

In order to build GTK+ you will need:

You will also need various dependencies, based on the platform you are building for:

If you are building the X11 backend, you will also need:

  • Xlib, and the following X extensions:
    • xrandr
    • xrender
    • xi
    • xext
    • xfixes (optional)
    • xcursor (optional)
    • xdamage (optional)
    • xcomposite (optional)
  • atk-bridge-2.0

If you are building the Wayland backend, you will also need:

  • Wayland-client
  • Wayland-protocols
  • Wayland-cursor
  • Wayland-EGL

Once you have all the necessary dependencies, you can build GTK+ by using Meson:

$ meson _build .
$ cd _build
$ ninja

You can run the test suite using:

$ meson test

And, finally, you can install GTK+ using:

$ sudo ninja install

Complete information about installing GTK+ and related libraries can be found in the file:

docs/reference/gtk/html/gtk-building.html

Or online

How to report bugs

Bugs should be reported to the GNOME bug tracking system. You will need an account for yourself.

In the bug report please include:

  • Information about your system. For instance:

    • which version of GTK+ you are using
    • what operating system and version
    • for Linux, which distribution
    • if you built GTK+, the list of options used to configure the build

    And anything else you think is relevant.

  • How to reproduce the bug.

    If you can reproduce it with one of the test programs that are built in the tests/ subdirectory, that will be most convenient. Otherwise, please include a short test program that exhibits the behavior. As a last resort, you can also provide a pointer to a larger piece of software that can be downloaded.

  • If the bug was a crash, the exact text that was printed out when the crash occurred.

  • Further information such as stack traces may be useful, but is not necessary.

Contributing

Patches should also be submitted to the bug tracking system. If the patch fixes an existing bug, add the patch as an attachment to that bug report; otherwise, enter a new bug report that describes the patch, and attach the patch to that bug report.

Patches should be in Git-formatted form. You should use git format-patch to generate them. We recommend using git-bz.

For more information on the recommended workflow, please read this wiki page.

Please, follow the CODING_STYLE document in order to conform to GTK+'s coding style when submitting a code contribution.

Release notes

The release notes for GTK+ are part of the migration guide in the API reference. See:

Licensing terms

GTK+ is released under the terms of the GNU Lesser General Public License, version 2.1 or, at your option, any later version, as published by the Free Software Foundation.

Please, see the COPYING file for further information.