Files
gtk/gdk
Ryan Lortie a00a5ed210 GtkApplication: avoid using stale timestamps
Avoid using a stale timestamp (from the last user interaction with the
application) when a message arrives from D-Bus requesting that a new
window be created.

In this case the most-correct thing that we can do is to use no
timestamp at all.

We modify gdk_x11_display_set_startup_notification_id() to allow a NULL
value to mean "reset everything" and then call this function
unconditionally on receipt of D-Bus activation requests.  The result
will be that a missing desktop-startup-id in the platform-data struct
will reset the timestamp.

Under their default configuration metacity and mutter will both map
windows presented with no timestamp in the foreground.  This could
result in false-positive, but there is very little we can do about that
without the original timestamp from the user event.

https://bugzilla.gnome.org/show_bug.cgi?id=752000
2015-07-14 18:34:09 -07:00
..
2015-07-01 21:07:28 +02:00
2015-02-02 09:28:22 +01:00
2014-10-13 10:43:31 -04:00
2015-05-08 14:21:11 -04:00
2015-05-08 13:34:25 -04:00
2015-01-17 01:03:10 -05:00
2014-09-01 19:17:53 +02:00
2014-09-01 19:17:53 +02:00
2014-06-11 21:55:15 -04:00
2014-02-07 13:06:10 -05:00
2015-03-22 14:40:57 -04:00
2015-02-12 17:51:31 +00:00
2014-11-06 12:24:43 +01:00
2013-04-19 20:11:39 -04:00
2013-04-19 20:11:38 -04:00
2013-04-19 20:11:38 -04:00
2014-02-19 18:56:05 -05:00
2014-06-11 21:55:15 -04:00
2014-05-22 09:31:15 -04:00
2014-08-30 00:53:21 -04:00
2014-09-24 20:34:16 -04:00
2014-06-11 21:55:15 -04:00
2015-03-22 02:10:23 -04:00
2014-09-07 17:14:37 -04:00
2014-06-11 21:55:15 -04:00
2015-06-23 17:27:42 -04:00
2015-06-23 17:27:42 -04:00
2013-07-17 17:52:19 -04:00
2015-02-02 09:28:22 +01:00