Closed bmihaila closed 11 years ago
Στις 19/03/2013 11:41 πμ, ο/η Bogdan Mihaila έγραψε:
Hi
Finally got some time to try out the "fullscreen plamoid". It is really nice and I would maybe switch to it while keeping the plasmoid in the tray but at the moment I cannot because the kwin script is very slow compared to the plasmoid. I mean even moving the VD selection by keyboard lags behind. I think this is just an issue with plasma and its fullscreen containments as I have similar issues with other plasmoids that use a fullscreen component. There are some workarounds to speed things up, like using a non-transparent background but then it misses some of its appeal ;). Anyways, the kwin script is very nice and like I said it should maybe be the future of the workflows project as managing your desktops is something that should be done in fullscreen mode. In a similar thinking like the zoom-UI of the old plasma/kwin activities. The performance issue is something that will eventually go away as KDE plasma libs become better or will anyways only affect a subset of the users with slower graphic cards. I am having the standard embedded intel graphics chip btw.
You could try to use the raster graphics system and not the native. I had the same issue and fixed by this. Desktop Effects -> Advanced -> Qt Graphics system: Raster
Now to the bug ;). When having the script activated through the kwin preferences I get the impression that it steals the active state marking from any other window even when it is not triggered to be shown. This can be seen only if you have the kwin effect "dim inactive" set as that darkens inactive windows. So if I have the workflow script activated I cannot get any window to not be inactive. I can interact with the windows but they are all darkened by that effect. When changing from one desktop to another it takes like one second to change the window from active to inactive and thus make it dark. Hope you can reproduce.
—
In some cases even though the window in the script is not appearing, it has been triggerred to be shown. Try pressing ESC to see if it will loses focus. Taking active state is important because otherwise no keyboard works in the kwin script window.. e.g. you cant even rename activities and workareas....
Well I reproduced, and you were right... It breaks also the Slide Back effect https://bugs.kde.org/show_bug.cgi?id=316831 but it is related with how kwin developers would like to behave this situation, we will see... I am very positive that this will be fixed for 4.11.x but I dont know for 4.10.x yet...
Ok, seems then that it might take some time to get fixed in KDE. Thx for telling, will stay with the plasmoid for now.
About the raster graphics system, last time I tried it, it wasn't soo fast either but maybe I should give it another try.
The issue yesterday was traced to be in a very specific library which can not be used with kwin scripts. That means that if I dont change the window implementation handling, is never going to be fixed... :)
I hope that in a few days I will have a new implementation for the windows handling to test... Some few minor bugs may arise afterwards because of that but there is no other way to go... I definitely want the kwin script available in 0.4.0 because it will track some more attention in the project...
this is fixed with help from the kwin developers... only issue remains because of the new implementation is that the kwin script can not catch the activitiesChanged signal from outside the script. But if you change activities for your windows from inside the kwin script there is not problem at all.. There is a chance that there will be a fix in 4.10.2 for this... we will see...
But if you change activities for your windows from inside the kwin script there is not problem at all..
Do you mean using the keyboard shortcuts to change activities will cause the script to not know it thus showing a different VD as selected?
No no... If you didnt have WorkFlow to change activity for a window, one way to do it is to right click on the window title and under Activities menu to set, for which Activities you would like your window to be shown.... That creates a signal for the window (activitiesChanged) but in kwin scripting there isnt such support yet so the kwin script doesnot update the window relevant Workareas. KWin developers said that there is a chance for this to be ported in 4.10.2 and not wait until 4.11 .
But if you drag your windows from inside WorkFlow kwin script to set in which Workareas to be shown there is not such problem... :)
Hi
Finally got some time to try out the "fullscreen plamoid". It is really nice and I would maybe switch to it while keeping the plasmoid in the tray but at the moment I cannot because the kwin script is very slow compared to the plasmoid. I mean even moving the VD selection by keyboard lags behind. I think this is just an issue with plasma and its fullscreen containments as I have similar issues with other plasmoids that use a fullscreen component. There are some workarounds to speed things up, like using a non-transparent background but then it misses some of its appeal ;). Anyways, the kwin script is very nice and like I said it should maybe be the future of the workflows project as managing your desktops is something that should be done in fullscreen mode. In a similar thinking like the zoom-UI of the old plasma/kwin activities. The performance issue is something that will eventually go away as KDE plasma libs become better or will anyways only affect a subset of the users with slower graphic cards. I am having the standard embedded intel graphics chip btw.
Now to the bug ;). When having the script activated through the kwin preferences I get the impression that it steals the active state marking from any other window even when it is not triggered to be shown. This can be seen only if you have the kwin effect "dim inactive" set as that darkens inactive windows. So if I have the workflow script activated I cannot get any window to not be inactive. I can interact with the windows but they are all darkened by that effect. When changing from one desktop to another it takes like one second to change the window from active to inactive and thus make it dark. Hope you can reproduce.