- Queries
- All Stories
- Search
- Advanced Search
Advanced Search
Apr 10 2020
Feb 2 2020
Dec 15 2019
Dec 14 2019
It was clazy, not me - just wanted to fix a memleak in kio :)
Dec 10 2019
Nov 7 2019
Oct 21 2019
I would also use CMAKE_CXX_STANDARD_REQUIRED to make sure the compiler actually *can* c++11, otherwise the flag is only added when the compiler supports it. Should not make much difference nowadays but since it's in ECM...
Sep 28 2019
In D23789#538985, @kossebau wrote:
- why has all Qt code not yet been adapted to QT_DEPRECATED_VERSION/QT_DEPRECATED_VERSION_X, are there places where those macros should not be used, but the version-less ones?
Because noone wanted to do the work and it was added late in the Qt5 lifetime -> A lot of stuff was deprecated for a long time already (in Qt4 times) and there is was a replacement since Qt5.0.0 so the macro was not needed (even though a lot of people got very angry about it). I added it for some new signals which created a lot of discussion since the old ones are widely used.
Can you point to those discussions? Would be curious to learn what people's thought are.
https://lists.qt-project.org/pipermail/development/2019-March/035343.html
Sep 27 2019
In D23789#536338, @kossebau wrote:Actual questions I have:
- why is QT_DEPRECATED_WARNINGS_SINCE not officially documented? like, any plans to change that macro to something else?
Just forgot it (and also the reviewers) I would guess. There is no plan to change it, at least none I'm aware of. I'm looking for an automatic generation of this macro. Since Qt6 switches to CMake I can maybe borrow some stuff from you ;)
Sep 23 2019
Aug 9 2019
Aug 1 2019
uploaded without arcanist to have 11 separate commits
Jul 31 2019
- svnqt/cache: use range-based for loops
- svnfrontend: use range-based for loops
- svnfrontend/models: use range-based for loops
- svnfrontend: use range-based for loops, use member-initialization instead custom ctors, use auto instead foo<bar>::iterator
- svnfrontend/svnactions: use range-based for loops
Jul 12 2019
Thx, this was an oversight from Qt4 porting.
Jul 10 2019
Jul 3 2019
Jun 1 2019
May 28 2019
May 3 2019
The you can also update your minimum Qt version to 5.9 - currently you've 5.7 which still supports gcc 4.6 which does not support 'override' so this requirement is no longer needed and can go away :)
Nov 26 2018
Oct 31 2018
Sep 22 2018
Aug 12 2018
May 16 2018
May 8 2018
Apr 4 2018
And why is m_scores not an object? No need for a pointer here I guess
Mar 30 2018
Mar 20 2018
Mar 15 2018
This should at least fix the most cases as described in the bug report :)