From kde-panel-devel Mon Nov 30 23:14:13 2015 From: David Edmundson Date: Mon, 30 Nov 2015 23:14:13 +0000 To: kde-panel-devel Subject: Re: Activity switching on window activation Message-Id: X-MARC-Message: https://marc.info/?l=kde-panel-devel&m=144892529219424 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--===============4888018198334642989==" --===============4888018198334642989== Content-Type: multipart/alternative; boundary=089e013cba0437fc1a0525ca346d --089e013cba0437fc1a0525ca346d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Mon, Nov 30, 2015 at 8:20 PM, Ivan =C4=8Cuki=C4=87 = wrote: > Hi all, > > A long time ago, we decided that out of the following options, the > first one was better: > > - (1) when a window is activated by external entity (a document opens > in an existing kate instance that is on a different activity to the > current one), kwin switches to the activity > - (2) --||--, kwin moves the window to the current activity > > I think we should "copy" the window not move. > I still think (1) is better than (2) and that it is a problem of > specific applications like kate that like opening everything in the > same window, and that those ought to be patched. > I know I'm getting a tiny bit off topic, but I just had a go at doing the proposed kate change. https://paste.kde.org/p4dymbtjr It's actually surprisingly hard, this is too hacky to ever merge. You can tell you have an instance already open, and you get told the DBus path for that existing instance, but there's no way to tell which activities that main window is on without then resorting to grabbing winIDs and probing X properties. BUT, a user made a nice point about why the current behaviour is wrong > - it is a bit of a privacy problem - the system can unexpectedly > switch to a different activity and reveal something that the user > didn't want to. > > While I'm still not for (2), we might consider another solution - when > the application opens up or activates a window in a non-current > activity, instead of automatically switching to that activity, we > might show a notification 'blah blah is open in blah blah activity' > with a button to switch to it. > > Thoughts? > > > Cheerio, > Ivan > > -- > KDE, ivan.cukic@kde.org, http://cukic.co/ > gpg key id: 850B6F76 > _______________________________________________ > Plasma-devel mailing list > Plasma-devel@kde.org > https://mail.kde.org/mailman/listinfo/plasma-devel > --089e013cba0437fc1a0525ca346d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Mon, Nov 30, 2015 at 8:20 PM, Ivan =C4=8Cuki=C4=87 <ivan.cukic@kde= .org> wrote:
Hi all,

A long time ago, we decided that out of the following options, the
first one was better:

- (1) when a window is activated by external entity (a document opens
in an existing kate instance that is on a different activity to the
current one), kwin switches to the activity
- (2) --||--, kwin moves the window to the current activity

I think we should "copy" the window not mov= e.

=C2=A0
I still think (1) is better than (2) and that it is a problem of
specific applications like kate that like opening everything in the
same window, and that those ought to be patched.

<= /div>
I know I'm getting a tiny bit off topic, but I just had a go = at doing the proposed kate change.

https://paste.kde.org/p4dymbtjr

It&= #39;s actually surprisingly hard, this is too hacky to ever merge.

Y= ou can tell you have an instance already open, and you get told the DBus pa= th for that existing instance, but there's no way to tell which activit= ies that main window is on without then resorting to grabbing winIDs and pr= obing X properties.


BUT, a user made a nice point about why the current behaviour is wrong
- it is a bit of a privacy problem - the system can unexpectedly
switch to a different activity and reveal something that the user
didn't want to.

While I'm still not for (2), we might consider another solution - when<= br> the application opens up or activates a window in a non-current
activity, instead of automatically switching to that activity, we
might show a notification 'blah blah is open in blah blah activity'=
with a button to switch to it.

Thoughts?


Cheerio,
Ivan

--
KDE, ivan.cukic@kde= .org, http://cukic.co/
gpg key id: 850B6F76
_______________________________________________
Plasma-devel mailing list
Plasma-devel@kde.= org
https://mail.kde.org/mailman/listinfo/plasma-devel=

--089e013cba0437fc1a0525ca346d-- --===============4888018198334642989== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KUGxhc21hLWRl dmVsIG1haWxpbmcgbGlzdApQbGFzbWEtZGV2ZWxAa2RlLm9yZwpodHRwczovL21haWwua2RlLm9y Zy9tYWlsbWFuL2xpc3RpbmZvL3BsYXNtYS1kZXZlbAo= --===============4888018198334642989==--