[Development] CI fails because a memory isn't allocated

2014-02-06 Thread Dmitry Ashkadov
Hello! I've tried to merge the patch https://codereview.qt-project.org/72692, but CI fails. There is a line in logs: cc1plus.exe: out of memory allocating 408 bytes How may it be fixed? Thank you! ___ Development mailing list Development@qt-project.o

Re: [Development] Qt 5.2 Testing (System tray)

2013-10-14 Thread Dmitry Ashkadov
Qt4 systray works in Gnome shell and KDE, Qt5 systray doesn't work in Gnome shell and KDE. About 1 month ago I tested Qt5 systray (from dev branch) and it didn't work. Maybe it is general problem of Qt5 systray implementation? 14.10.2013 19:10, Jiergir Ogoerg ?: But the Qt4's systray works

Re: [Development] QtTest for everybody

2013-10-08 Thread Dmitry Ashkadov
07.10.2013 23:27, Thiago Macieira пишет: > On segunda-feira, 7 de outubro de 2013 22:50:49, Dmitry Ashkadov wrote: >> The topic about exceptions for slots and signals has inspirited me to >> pay your attention to QtTest. QtTest is a good unit-test framework, but >> it is f

[Development] QtTest for everybody

2013-10-07 Thread Dmitry Ashkadov
Hello! The topic about exceptions for slots and signals has inspirited me to pay your attention to QtTest. QtTest is a good unit-test framework, but it is focused to Qt. I think QtTest may be used for any project, moreover it may be used as unit testing framework for project that doesn't use Q

Re: [Development] [Feature] Q_INFO: Annotations for classes, methods, properties and enums

2013-09-08 Thread Dmitry Ashkadov
Hello! I don't know how this may work, but I think you should be careful with commas inside Q_INFO. If Q_INFO may be a simple "empty" macro, then preprocessor may require 2 arguments for Q_INFO macro in Q_INFO("foo", "bar") and Q_INFO(myTag ("foo", "bar")). 01.09.2013 15:20, Stefan Merettig п

Re: [Development] Making QScopedPointer scoped (again)

2013-09-05 Thread Dmitry Ashkadov
05.09.2013 04:00, Thiago Macieira пишет: > We should add QUniquePointer only when we find the need for it in Qt code, > which by our rules cannot depend on the C++11 standard library features. Maybe I don't understand something, but Does Qt use QScopedPointer in its implementation? Why Qt doesn'

Re: [Development] Making QScopedPointer scoped (again)

2013-09-04 Thread Dmitry Ashkadov
04.09.2013 09:36, Olivier Goffart пишет: > > It is unfortunate that the standard did not choose the name > std::scoped_pointer, but that's not the first time the standard and Qt are > using different name (QByteArray <> std::string, QLinkedList <> std::list, > ...) I think, there is a real reas

Re: [Development] Making QScopedPointer scoped (again)

2013-09-04 Thread Dmitry Ashkadov
Hello! 03.09.2013 15:33, Stephen Kelly ?: On Tuesday, September 03, 2013 12:48:51 Daniel Teske wrote: *const* unique_ptr is a scoped ptr. So QScopedPointer is a NIH irregardless of a move support. First of all, I think, you should define what is a 'scoped'. A const unique_ptr is like a

[Development] One more possible CMake related problem

2013-07-23 Thread Dmitry Ashkadov
Hello! Here is a piece of code of qtbase/mkspecs/features/data/cmake/Qt5BasicConfig.cmake.in : !!IF isEmpty(CMAKE_DLL_DIR_IS_ABSOLUTE) set(imported_locati