In D26338#588960, @davidedmundson wrote:On the conceptual level, does it make more sense for the relevant client (konsole) to monitor for compositing changed itself. It's something that could change at runtime regardless, so it needs to react to it anyway?
If it does need that code anyway, there's no point doing fixes in startkde
- Queries
- All Stories
- Search
- Advanced Search
Feed Advanced Search
Advanced Search
Advanced Search
Jan 7 2020
Jan 7 2020
Jan 2 2020
Jan 2 2020
bits_per_rgb_value was 11, and the max values were all set to 2047. Total 33 bits per pixel, this is just insane. Now it's all trimmed down to 255.
Jan 1 2020
Jan 1 2020
Note that this is an RFC at the current state. This can be solved elsewhere (e.g. ksmserver), and is tested only on X11 (I don't have machine that runs wayland w/o problems). I also don't like that plasma-session is calling QGuiApplication, which is required to use KWindowSystem.
Dec 11 2019
Dec 11 2019
Sorry for hailing, Alexey, but you're the original author, and it looks like you're the only one who already understands this part.
esjeon added a reviewer for D25876: Correctly populate max color values in server screen format: alexeymin.
Nov 14 2019
Nov 14 2019
Thanks all. I hope I can be of help.
Can you provide your email address
Do you have commit access?
In D25307#562618, @davidre wrote:In D25307#562613, @esjeon wrote:What shortcuts had you in mind to delete?
My specific interest is deleting shortcuts of removed KWin scripts. ( e.g. https://github.com/esjeon/krohnkite/issues/31 ) Such shortcuts keep appearing on Global Shortcuts dialog unless manually deleted. Also, while developing the script, I leave garbage values behind, and having this around will be handy.
As noted in that issue for removing shortcuts modifying kglobalshortcutsrc is not enough as kglobaccel will write back. A reliable way to do that is via DBus.
What shortcuts had you in mind to delete?