Fallback to _NET_WM_PID to map windows to activitieshtml2

Most toolkits supports that property, so this allows to
write activities without setting our own custom properties,
which is very handy if you are not using python or are not
able to go that low level.

This is similar to what gnome-shell is doing. Simplifying
a bit their logic to map windows to applications is

1 Check WM_CLASS
2 Check _NET_WM_PID
3 Check startup notification properties

Now 1 is not good enough for us. They map multiple windows
to the same application, while for us every window is a
separate activity. About 3, we don't currently implement
startup notification but we could in the future. In that
case it could just be a fallback.

It probably make sense to keep our own custom properties
as 1, for complicated cases like running the window in a
subprocess.

0 files changed, 0 insertions, 0 deletions