- User Since
- May 8 2015, 2:33 PM (124 w, 2 d)
Fri, Sep 22
Thinking of it, wouldn't it make total sense to have this as a QtQuick-only KCM, i.e. using KQuickAddons::ConfigModule?
Maybe not put it in systemsettings, but tell users to run kcmshell to open it? That really hides it well though, also defeating the purpose...
Can we hide this even more, given that it's an utter expert setting?
Thu, Sep 21
Require at least Frameworks 5.39
Add runtime version check, this will only work with Frameworks 5.40 onwards...
Right. Will change...
A compile-time check doesn't buy us much, this line could be compiled in an still run against a kwayland lacking the crash fix.
FWIW, I tested it, it fixes kwin crashing when adding a setApplied() call on the OutputConfiguration, and it also means the applied signal arrives.
Yes, the initial idea was to send applied() to all connected resources. That is not s_allResources, so your patch is correct. The resources that are actually bound are not currently tracked.
Wed, Sep 20
Ow, see, I was exporting a different XDG_RUNTIME_DIR in my login procedure. I guess removing that fixes the problem as well. :)
That's happening when I start startplasmacompositor by hand, and it's annoying as fuck. Sure, I can add that to my login script, but it's literally the only thing that I have to do to make plasma/wayland come up. Everything else works. (Also, we do create XDG_CONFIG_HOME in the same script, so to me it makes sense to create XDG_RUNTIME_DIR as well (both are user-specific).
Please abandon, I've already fixed this in master.
Tue, Sep 19
Mon, Sep 18
One thought that comes up with me is that we don't necessarily target the main public. For the project to succeed at first, we don't need general audience size sales, we need to find one niche that we can serve really well. Thoughts:
Sat, Sep 16
Fri, Sep 15
Thu, Sep 14
First coverage appears:
Mon, Sep 4
Wed, Aug 30
Mon, Aug 28
Aug 24 2017
Be careful pushing, by the way. It seems you've branched this off of my rotationplasmoid branch. Should obviously go into master.
-1, we discussed this in a bugreport already recently. The rationale in there applies here, too. It's a conscious design choice made, and it's easy enough to ship a color scheme with more contrast.
This one slipped my attention. I think it's still relevant?
Patch looks fine, other than the heuristics @broulik already pointed out.
Aug 17 2017
Aug 16 2017
Some coding style suggestions
Aug 15 2017
This UI change should be addressed with the new KScreen KCM, btw.
This code is on its way out though, pending my forever-taking kscreen kcm rewrite. Since that's not going fast, I don't want to block progress on the currently shipped version.