summaryrefslogtreecommitdiffstats
path: root/tests/auto/qwidget
Commit message (Collapse)AuthorAgeFilesLines
* tst_qwidget widgetAt now does not leave widget lowered if test failsGareth Stockwell2009-11-041-2/+3
| | | | | Task-number: QTBUG-5396 Reviewed-by: axis
* Merge commit 'widget/4.6' into origin/4.6Olivier Goffart2009-10-301-0/+45
|\ | | | | | | | | Conflicts: src/gui/effects/qgraphicseffect.cpp
| * Fix tst_QWidget::compatibilityChildInsertedEvents testBjørn Erik Nilsen2009-10-291-0/+3
| | | | | | | | | | | | | | | | | | This broke after commit: a8e2a457bb7d2fc377c1c65b6a4172974919e055 (Add a new event type, WinIdChange). The first thing that happens in show() is that the top-level is created, and hence we send WinIdChange. We therefore have to add this event to list of expected events. Reviewed-by: TrustMe
| * Wrong caching of opaque children in QWidget.Bjørn Erik Nilsen2009-10-281-0/+42
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The opaque children cache was clipped to all the ancestors up to the top-level, which means whenever a widget changes geometry all the children must be invalidated. However, the bug was that we didn't invalidate the children, and that is of course slow so we don't want to do it either. A better solution is to only clip the children cache to the widget itself (widget->rect() instead of widget->clipRect()), and we can perfectly do this because the region we subtract the opaque children from is already inside the clipRect(). Auto-test included. Task-number: QTBUG-4245 (related to)
* | Change all valid Task-Tracker references to bugreports.qt.nokia.com reference.Warwick Allison2009-10-291-1/+1
|/
* Fixed logical error in winIdChanged auto test.Gareth Stockwell2009-10-211-0/+15
| | | | | | | | | | | | | The test (see 02fbfdbd) previously asserted that changing the parent of a native widget caused a WinIdChange event on Symbian, but not on other platforms. The test now asserts that: 1. Changing the parent of a native widget causes a WinIdChange event on all platforms. 2. Changing the grandparent of a native widget causes a WinIdChange event only on Symbian. Reviewed-by: Paul Olav Tvete
* Merge branch '4.6' of git@scm.dev.nokia.troll.no:qt/qt-widget-team into 4.6Alexis Menard2009-10-201-4/+37
|\
| * Fixed a rare crash in qt_x11_enforce_cursorGabriel de Dietrich2009-10-151-0/+33
| | | | | | | | | | | | | | | | | | | | | | | | A QPointer was set to point to a QWidget by one of its children, during its deletion. This happens during the child deletion, and after the call to QObject::clearGuards(), which means that the QPointer becomes a dangling one. The fix ensures that qt_x11_enforce_cursor will not be called with a being-deleted QWidget. The included auto-test doesn't test anything, except that it doesn't crash. Reviewed-by: Olivier
| * Stabilize test on x11Olivier Goffart2009-10-151-4/+4
| |
* | fix bug in tst_qwidget.cppJoerg Bornemann2009-10-191-4/+6
| | | | | | | | | | | | WinIdChangeEventWidget::event didn't return a value in all codepaths. Reviewed-by: thartman
* | Merge commit 'origin/4.6' into mmfphononFrans Englich2009-10-161-14/+3
|\|
| * Fix some of the QWidget test on CocoaOlivier Goffart2009-10-131-14/+3
| |
* | Updated qwidget winId auto-testsGareth Stockwell2009-10-091-0/+144
|/ | | | | | | | | | | | | 1. Added a new test step, winIdChangeEvent, to test that QWidget::setWinId correctly sends WinIdChange events. 2. The persistentWinId test step check the following assertion: re-parenting a native widget causes its own winId to change, but not those of its (native) descendents. This assertion is not true for Symbian, so this test step has been replaced, on Symbian, by reparentCausesChildWinIdChange, which checks the inverse assumption, i.e. that the native descendents' winIds also change. Reviewed-by: Bjoern Erik Nilsen
* Merge branch '4.6' of scm.dev.nokia.troll.no:qt/qt into 4.6ninerider2009-10-061-1/+2
|\
| * Stabilize tests on X11Olivier Goffart2009-10-061-1/+2
| |
* | Skipped enter/leave test for Windows CEninerider2009-10-061-0/+3
|/ | | | | | Currently Windows has no proper cursor support. Reviewed-by: Thomas Hartmann
* Stabilize tests on X11Olivier Goffart2009-10-051-5/+5
|
* Stabilize test on X11Olivier Goffart2009-10-051-3/+2
|
* Stablilize autotests on X11Olivier Goffart2009-10-021-3/+8
|
* Stabilize the SyntheticEnterLeave tests.Paul Olav Tvete2009-10-021-0/+4
| | | | | | | Reset the mouse position to a known state at the start, instead of depending on what the previous test did. Reviewed-by: Jeremy
* Test stabilisation on X11Olivier Goffart2009-10-011-7/+11
| | | | | | for the Q3Table one, it sometimes fail with XPASS. There is no point trying to stabilize a failure on a test for a class we are not likely to touch anyway.
* Merge branch '4.5' of scm.dev.nokia.troll.no:qt/qt into 4.6Simon Hausmann2009-10-011-0/+82
|\
| * Fixed Designer property editor selection bug.Gabriel de Dietrich2009-10-011-0/+82
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When the editor had been created inside the QtPropertyEditorView (inheriting QTreeWidget), the subsequent show sent a synthetic mouse move event down to the QLineEdit, and a new selection was made on the text because the mouse button was marked as pressed in the event. QApplicationPrivate::sendSyntheticEnterLeave() now sends a mouse move event without any button pressed. Auto-test included in tst_QWidget. Task-number: QTBUG-4055 Task-number: 253159 Task-number: QT-659 Task-number: 245398 Reviewed-by: bnilsen
| * Update license headers again.Jason McDonald2009-09-083-12/+12
| | | | | | | | Reviewed-by: Trust Me
* | fix minimizing for Windows CE and Windows mobileJoerg Bornemann2009-10-011-10/+0
| | | | | | | | | | Task-number: QT-2243 Reviewed-by: thartman
* | Test http://codepaster-nokia.troll.no/?id=18722 skipped for WinCEninerider2009-10-011-0/+3
| | | | | | | | | | | | | | Test does not really make sense on WinCE as it is. Lists with items size over 5000 are not useful there. Reviewed-by: Joerg
* | Stabilize tests on X11Olivier Goffart2009-10-011-1/+1
| |
* | Fix qwidget auto test failing to build on OSX/carbon.Justin McPherson2009-10-011-2/+2
| | | | | | | | Reviewed-by: Sarah Smith
* | Stabilize tests on X11Olivier Goffart2009-09-301-22/+22
| |
* | Merge branch 'focusFixes' into 4.6axis2009-09-301-14/+5
|\ \ | | | | | | | | | | | | | | | Conflicts: src/gui/kernel/qwidget_p.h src/gui/kernel/qwidget_s60.cpp
| * | Avoided qt3support constructor (S60 port doesn't have it).axis2009-09-301-1/+1
| | | | | | | | | | | | RevBy: Paul Olav Tvete
| * | Helped out the Symbian compiler to avoid build error.axis2009-09-301-4/+4
| | | | | | | | | | | | RevBy: Trust me
| * | Revert "Switched to asynchronous focus handling on Symbian."axis2009-09-301-9/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This reverts commit b6377f43410b14125a66ffd02acde69cfb6e455e. The asynchronous handling caused too many headaches with input methods, which expect the focus status to be updated immediately. This may break the test case that was originally fixed by this patch (I cannot find out which one at the moment), but that will have to be solved in a different way. Conflicts: src/corelib/kernel/qcoreevent.cpp src/corelib/kernel/qcoreevent.h src/gui/kernel/qwidget.cpp src/gui/kernel/qwidget_p.h src/gui/kernel/qwidget_s60.cpp
* | | Merge commit 'qt/4.6' into mmfphononFrans Englich2009-09-291-46/+57
|\| |
| * | Make the test pass on both large and small screens.Paul Olav Tvete2009-09-281-10/+10
| | | | | | | | | | | | Reviewed-by: Joerg
| * | Stabilize some more testsOlivier Goffart2009-09-281-9/+11
| | |
| * | Fixes for Windows CE.ninerider2009-09-251-33/+42
| | | | | | | | | | | | | | | | | | | | | | | | Tests showAndMoveChild and rectOutsideCoordinatesLimit_task144779 were made desktop client area dependent so the screen capturing targets meaningfull rectangles on Windows CE. Reviewed-by: Joerg
* | | Merge commit 'qt/4.6' into mmfphononFrans Englich2009-09-241-110/+138
|\| |
| * | Stabilize more testsOlivier Goffart2009-09-231-88/+89
| | |
| * | Fix tst_QWidget::activateWindow on X11Olivier Goffart2009-09-231-5/+6
| | | | | | | | | | | | | | | | | | On X11 one needs to wait logner for the reply for the window mabager All the QWidget tests passes on my X11 in about 30seconds now
| * | Skip tst_QWidget::setWindowGeometry on X11Olivier Goffart2009-09-231-0/+10
| | | | | | | | | | | | | | | | | | | | | Since WindowManager operation are all assync, and we have no way to know if the window manager has finished playing with the window geometry, this test can't be reliable. Reviewed-by: Denis
| * | Stabilize tst_QWidget::saveRestoreGeometryOlivier Goffart2009-09-231-21/+37
| | | | | | | | | | | | | | | We need to wait for more condition before saving, otherwise what we save is not accurate (and the test fails)
* | | Align with Qt coding style.Frans Englich2009-09-241-0/+1
|/ /
* | Fix tst_QWidget::showMaximized on X11Olivier Goffart2009-09-231-1/+1
| | | | | | | | | | | | On X11 We have to wait we get the size change from the window manager Reviewed-by: Jason Barron
* | Try to stabilize and speedup the qwidget testOlivier Goffart2009-09-221-516/+378
| | | | | | | | | | | | | | The test goes in only almost 30seconds now. But i still have few failures Reviewed-by: Denis
* | Make test pass on WindowsPaul Olav Tvete2009-09-151-1/+3
| | | | | | | | Reviewed-by: Jan-Arve
* | Fix tst_QWidget::inputFocus_task257832 on WindowsJan-Arve Sæther2009-09-151-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | The widget must be created before calling QInputContext::setFocusWidget. Otherwise we run into an assertion. Yes, this only occurs in debug configuration but its still annoying... Cherry-pick of commit d6b8f81a2440e7a507ecbb1becd90ef284510787 from master. Reviewed-by: thartman Conflicts: tests/auto/qwidget/tst_qwidget.cpp
* | Implement synthetic enter/leave events for QWS.Paul Olav Tvete2009-09-141-2/+3
| | | | | | | | | | | | | | QWS uses alien widgets too, so we need the same logic as the other platforms. Reviewed-by: bnilsen
* | Fixed QWidget::activateWindow for Symbian.Janne Anttila2009-09-111-11/+47
| | | | | | | | | | | | | | | | | | | | | | | | | | | | activeWindow documentation says: "active window is a visible top-level window that has the keyboard input focus" and "If you want to ensure that the window is stacked on top as well you should also call raise(). Note that the window must be visible, otherwise activateWindow has no effect." What we were doing earlier was basically raise. Now we just set the keyboard focus to underlying native window. Task-number: 260685 Reviewed-by: Jason Barron
* | Fixed QWidget::setWindowState for Symbian.Janne Anttila2009-09-112-0/+44
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-29 14:22:48 +0000