- User Since
- Jun 9 2015, 5:16 PM (235 w, 2 d)
Thu, Nov 14
Nov 11 2019
Fixed masks as well, now even some more complex XCF files work again.
Forgot to fix the layer offset reading, and read the precision after instead of before the image properties
Oct 11 2019
Any reason not to use kexiv2?
Something like this I think should work:
Already fixed with another approach in master.
Oct 5 2019
Oct 2 2019
Aug 3 2019
Jul 31 2019
Jul 23 2019
Jul 15 2019
Jul 7 2019
Created a merge request here, I think I did it right: https://invent.kde.org/kde/konsole/merge_requests/12
Jul 5 2019
You'll have to throw in a bunch of qAsConst() to silence clazy and the code ends up less readable imho. So I actually like Q_FOREACH better if you want to make clazy shut up as well (but in general I think clazy is a bit too triggerhappy, readable code is more important than fast code, if it is too slow you bring out a profiler and fix where the problems are).
May 26 2019
May 12 2019
Mar 8 2019
Mar 4 2019
Mar 2 2019
How about just a checkbox to turn on/off the new "fancy" search look for now? I've tested with all the color schemes I have available, and I believe we handle it OK, but I could have missed some.
updated so it applies cleanly
Updated so it applies cleanly.
FWIW, looking at the code briefly, I think this patch does the right thing if we end up in that bad "something went wrong"-state. But there's probably a second bug somewhere that leads us to that state, so a bit hard to reproduce, I guess.
Removing the changing the lightness of the buttonColor makes it a bit more visible, imho: