- User Since
- Apr 19 2015, 12:29 AM (272 w, 1 d)
Fri, Jul 3
I feel like it would be a good moment to pick up this again, @ltoscano what do you think?
Wed, Jun 24
Any special reason it's called "No. 2"? Is there a No 1 somewhere?
Yes :) - No. 1 is a slightly modified version of my original proposal, which I uploaded here: https://www.pling.com/p/1397003/.
Ok, i guess you can commit it.
Thu, Jun 18
Wed, Jun 17
Tue, Jun 16
Sat, Jun 13
Given the current state of instability we have due to the gitlab migration + different structure fallout, let's give us a few weeks to try to stabilize things and come back to this?
Thu, Jun 11
Yes i understand the scripts are shared between gitlab and jenkins and that lots of projects are not "very good" in keeping their tests clean, that's why i asked this to be opt-in for those projects that try to actually have passing tests :)
Wed, Jun 10
Tue, Jun 9
Sun, Jun 7
Jun 4 2020
oh i think i'm too late :D
It didn't really land on Qt 5.15 yet, so we may need to update the comment to say 5.15.1 or something
Jun 3 2020
Jun 2 2020
Jun 1 2020
May 31 2020
May 30 2020
May 26 2020
May 25 2020
May 24 2020
Potential solution, just drop CHM support https://tsdgeos.blogspot.com/2020/05/chmk-simple-chm-viewer.html
Personally I'm happy enough with this, i guess wait a few days and if noone disagrees, land it
May 23 2020
Do you think we should mention something like
May 22 2020
Now i understand this is causing relatively several issues, sorry for dropping the ball, so we should probably fix for users before Qt 5.15.1
Not sure if you're subscribed to https://phabricator.kde.org/D22488 see my last comment there i think it's the way to go
Wouldn't it make more sense to fix in Qt?
I don't think moving this code from KIconThemes to kmainwindow makes sense, what about all the apps that use KIconThemes but no KMainWindow?