You are not logged in.
I have been playing around with deepin DE for a little while. So far I am impressed with it for the most part. It's just some small issues that is anoying me.
One of those is that windows don't get raised up when I click inside the window and it gets focus. Only when I click on the titlebar will the window get raised up above others. I found this to be a little anoying.
I have googled around for a while trying to search for a solution, but so far I haven't found any.
I have tryed using gconf-editor. With it I have found settings around this. I can successfully set focus to follow the mouse, and then windows will rise up as fast as I point the mouse on them and they get focus. But that setting is somewhat invalid when the default (and prefered) method "click-to-get-focus" is choosen.
Does anybody have a good idea or tips?
Last edited by shellback (2016-07-14 16:39:23)
Offline
Install dconf-editor and check "com>deepin>wrap>gnome>desktop>wm>preferences>raise-on-click" is set to true.
That should be the default value and works fine for me.
MODS: maybe it would be best to merge this thread into 'main' arch-deepin thread?
https://bbs.archlinux.org/viewtopic.php?id=181861
Last edited by metak (2016-06-11 08:48:50)
Offline
Sorry, I meant that I had installed dconf-editor...
That value is true
I have tried to set it to false and switch back to true without making any difference.
Offline
Try creating a new user account, start dde and see if it still persists? I can't reproduce this issue on my end.
Offline
Hi again, sorry the delay...
I have tried creating a new user, but unfortantly that didn't help either. Still got same weird behavior
Offline
Hi again, sorry the delay...
I have tried creating a new user, but unfortantly that didn't help either. Still got same weird behavior
Then you should try reporting this issue upstream, because it could be a bug.
https://github.com/linuxdeepin/developer-center/issues
Last edited by metak (2016-06-12 18:02:23)
Offline
Now with the latest update of deepin-mutter to 3.20 the problem is gone...
Marking it as Solved
Offline