Files
gtk3/gdk
Carlos Garnacho 0d30ad279f wayland: Separate selection buffers and other per-selection atom data
This has most notably impact in selection buffers, because those were
shared across all selection atoms. This turned out wrong on 2 situations:
- Because the selection atom was set at SelectionBuffer creation time, the
  GDK_SELECTION_NOTIFY events generated will have unexpected info if the
  buffer is attempted to be reused for another selection.
- Anytime different selections imply different stored content for the same
  target.

This is better separated into per-selection buffers, so it's not possible
to get collisions if a same target is used across different selections.

https://bugzilla.gnome.org/show_bug.cgi?id=768177
2016-06-30 14:10:26 +02:00
..
2016-06-29 15:10:39 +02:00
2016-06-09 17:45:40 +01:00
2016-06-09 17:45:40 +01:00
2016-05-17 14:16:39 -04:00
2016-06-01 09:31:17 -04:00
2016-05-26 12:46:54 +01:00
2016-05-08 15:34:28 +02:00
2016-06-09 17:45:40 +01:00
2016-05-10 15:32:25 -04:00
2016-04-30 21:06:38 -04:00
2016-05-23 08:34:17 +01:00
2016-04-25 12:29:36 +01:00
2016-04-15 22:22:48 -04:00
2016-05-08 15:34:28 +02:00
2016-04-27 23:18:16 -04:00
2016-04-18 11:46:58 -04:00
2015-10-03 22:26:27 -04:00
2016-06-09 17:45:40 +01:00
2016-06-09 17:45:40 +01:00