summaryrefslogtreecommitdiffstats
path: root/tests/auto/qwidget/qwidget.pro
Commit message (Collapse)AuthorAgeFilesLines
* tests: allow unstable tests to be marked with CONFIG+=insignificant_testSergio Ahumada2011-12-281-0/+2
| | | | | | | | | | Marking a test with CONFIG+=insignificant_test will cause the exit code of the test to be discarded during `make check'. This is intended to be used for tests which are valuable to run, but are known to be unstable and are not feasible to immediately fix. Change-Id: Id7b2407d0a13c8de19a58badb78fa7c018c9b50a Reviewed-by: Jo Asplin
* Autotests: if you use X11 libs, you must link to X11 libs explicitly.Thiago Macieira2010-03-211-0/+4
| | | | | Solaris linker complains if you don't. Plus it's the right thing to do
* Fix qwidget auto test failing to build on OSX/carbon.Justin McPherson2009-10-011-2/+2
| | | | Reviewed-by: Sarah Smith
* Fixed QWidget::setWindowState for Symbian.Janne Anttila2009-09-111-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | Before this commit calling setWindowState(Qt::WindowFullScreen) on a widget instance affected all new widget instances created after this method. This bug happened due to fact that window decorations i.e. statuspane and softkeys visibility was only changed when switching to or from fullscreen state. In the reported bug it happened that second widget was initially in Qt::WindowNoState and it was changed to Maximized. Since window decorations are global not window specific at the moment, the default decoration visibility for second window is the one to which previous window has set them. In this case previous window was in fullscreen and that's why the decorations were visible also for second maximized window. Probably the right fix would be to change the decoration to window specific but that is quite a big change and for now the bug is fixed with this commit. Autotest: Excluding new test case, same results before and after. Task-number: 261048 Reviewed-by: Jason Barron
* Long live Qt for S60!axis2009-04-241-0/+21