| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
On mac, we always get full update.
|
| |
|
|
|
|
| |
When a widget is shown we get two paint avent on Mac
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The timer interval used currently on Windows is 16 ms, but we get ticks
at every 32 ms on average, so the consistent timing is not reliable on windows.
We should use the multimedia timer instead (use 15 ms for QTimer), once
qt is able to handle events while native event loops are running.
When this is done, the ifdefs introduced in this commit should be removed.
Reviewed-by: thierry
|
|
|
|
|
|
|
| |
Here lot of views were floating around and the processEvent was not
called in the right place.
Reviewed-by:ogoffart
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Added setOriginatingObject() and originatingObject() to QNetworkRequest
that internally tracks the QObject using a QWeakPointer.
Reviewed-by: Lars Knoll
Rubberstamped-by: Thiago
|
| |
| |
| |
| |
| |
| |
| |
| | |
This is definitely a compiler bug. The compiler forgets to adjust the
value of the pointers inside the template operator== function. If you
make the call outside the template function, it works as expected.
Reviewed-by: Trust Me
|
| |
| |
| |
| |
| |
| |
| | |
The problem was that we forward-declared as struct, but the function was
implemented as class. It's different on MSVC.
Reviewed-by: Trust Me
|
| |
| |
| |
| | |
Reviewed-by: TrustMe
|
| |
| |
| |
| | |
Reviewed-by: alexis
|
| |
| |
| |
| |
| |
| | |
The signal handler does seem to work on Mac for segfault
Reviewed-by: Rohan McGovern
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
Events caused by dragging a mouse are currently unavailable in
Windows Mobile.
Reviewed-by: Joerg
|
| |\ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
...on mac. Since mouse wheel events are accelerated by the OS on mac,
we cannot multiply the delta with QApplication::wheelScrollLines,
since this will make scrolling behave far to fast. To change the
speed of wheel events on Mac, one should use system preferences.
This patch updates the test to reflect his difference.
Rev-By: ogoffart
|
| | |
| | |
| | |
| | |
| | |
| | | |
Timing issues prevent this test from working correctly on Windows CE.
Reviewed-by: Joerg
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The 'fuzzy' value for the was not relaxed enoough for small devices
such as Windows Mobile and the like.
Reviewed-by: Joerg
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Commit fc3dfc20d487cb4fd2f93bd9fa36eef85a7467a3 fixes the problem.
The unpolished items list was modified in between the iteration
which means that invokeMethod was never recall if you add an item
inside the polishEvent handler. The invokeMethod is called in addItem
only when the list is empty right before we add the item in the list.
Task-number:QTBUG-4439
Reviewed-by:TrustMe
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This patch make sure that we always start from the beginning of
the unpolished items list and we erase the first value at each iteration.
The patch also convert the list to a set that is more appropriate here.
Merge-request: 1707
Reviewed-by: Alexis Menard <alexis.menard@nokia.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This fixes a weird bug when pressing the menu key on a proxy that
embed a lineedit (but the proxy don't have the focus).
At each time the key was pressed a context menu was created. When we press
the menu key, QWidgetMapper will create a context menu event that will be
sent to the QGraphicsView and will end up in QGraphicsScene.
QGraphicsScene will then try to find all items under the mouse and will
try to find any item from this list that accept this contextMenuEvent.
In our case the proxy will always accept it and therefor will always send
it to the widget that it owns and that's why we had this infinite numbers
of QMenu. In QWidget world the context menu event is always sent to the
widget that has the focus. If you checked any QWidget subclasses you'll
see that all of them assume that when they get a context menu event
everything is fine focus wise. We could have changed
QGraphicsScene::contextMenuEvent but this will breaks some existing code.
Instead we just checked that QGraphicsProxyWidget has the focus
before we actually send the contextMenuEvent to the widget it owns.
I have modified an existing auto-test to cover that. Be careful
widget->setContextMenuPolicy(Qt::ActionsContextMenu) means that you will
get no contextMenuEvent. :D. In this test i cover the standard use case
and the one with Qt::ActionsContextMenu with and without the focus on the
proxy.
Task-number:QTBUG-3787
Reviewed-by:jan-arve
|
|\ \ \
| | |/
| |/| |
|
| |/
| |
| |
| | |
Reviewed-by: TrustMe
|
| |
| |
| |
| | |
Reviewed-by: Miikka Heikkinen
|
| |
| |
| |
| | |
Reviewed-by: TrustMe
|
| |
| |
| |
| |
| |
| |
| | |
Make tst_QTextLayout::testTabDPIScale work by increasing the tab
stop distances. Now, systems with higher DPIs can pass this test.
Review-By: Joerg Bornemann
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
| |
When there are only pause animations running, the timer will stop and
restart when the closest pause animation finishes. While there are only
pause animations running, there are no additional timer ticks, but
if there is at least one animation running that is not a group or a pause,
then the global animation timer will restore it's update interval.
Includes a new auto-test for the QPauseAnimation class.
Task-number: QT-941
Reviewed-by: thierry
Reviewed-by: janarve
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
This reverts commit bf8d74bb8e849cb9eea74ef8fdb82d8926c48880.
Breaks more cases than it actually fixes.
modified: tests/auto/qtextlayout/tst_qtextlayout.cpp
|
|/
|
|
|
|
|
|
| |
The test data does not account for different geometries on different
devices. The 'magic number' 89 would have to be adapted for each
variant. A more robust test would be required to suit all cases.
Reviewed-by: banana joe
|
|
|
|
|
|
|
| |
Symbian has a different default font size than other OSses.
Consider that fact in tst_QTextLayout::testTabDPIScale
Reviewed-By: Liang QI
|
|
|
|
|
|
| |
We need to test through extension tool button and menu for it when there is no enough width on embedded devices.
Reviewed-by: TrustMe
|
|
|
|
| |
Reviewed-by: TrustMe
|
|
|
|
|
|
|
|
|
|
|
| |
Cetest (and other programs that upload dlls manually without using a
package) need to deploy some plugins for specific tests. If those
tests are deployed in a normal package however, the installation will
fail because the plugins are already included in the Qt installation.
Fixed that by putting the deployment inside a scope that cetest will
define.
RevBy: Miikka Heikkinen
|
|\ |
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
Now supported after float patches.
Signed-off-by: Eduardo M. Fleury <eduardo.fleury@openbossa.org>
Reviewed-by: Jesus Sanchez-Palencia <jesus.palencia@openbossa.org>
|
| |
| |
| |
| |
| |
| |
| |
| | |
Now we don't support floating items and so we should consider
that the layout has a conflict when handling this situation.
Signed-off-by: Jesus Sanchez-Palencia <jesus.palencia@openbossa.org>
Reviewed-by: Caio Marcelo de Oliveira Filho <caio.oliveira@openbossa.org>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Since the AnchorData cleanup commit (c974aca8) all anchor initialization
is being done by refreshSizeHints. However that method was not able
to properly initialize the internal layout anchors.
This commit refactors that method both to add the functionality and
improve readability.
Signed-off-by: Eduardo M. Fleury <eduardo.fleury@openbossa.org>
Reviewed-by: Caio Marcelo de Oliveira Filho <caio.oliveira@openbossa.org>
|
| |
| |
| |
| |
| |
| |
| |
| | |
Removing QEXPECT_FAIL and making minor corrections on expected
values.
Signed-off-by: Eduardo M. Fleury <eduardo.fleury@openbossa.org>
Reviewed-by: Artur Duque de Souza <artur.souza@openbossa.org>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Add autotests that use the ExpandFlag via QSizePolicy::Expanding
policy. Those tests cover the simple cases and behaviours with
sequential and parallel anchor setups.
Signed-off-by: Caio Marcelo de Oliveira Filho <caio.oliveira@openbossa.org>
Reviewed-by: Jesus Sanchez-Palencia <jesus.palencia@openbossa.org>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Add autotest which actually passes, the problem (in kurltest) was the underscore
in the hostname.
Rename ok_hostname to bad_hostname in the error test, for clarity.
Merge-request: 1710
Reviewed-by: Thiago Macieira <thiago.macieira@nokia.com>
|
| |
| |
| |
| |
| |
| | |
Enter leave signals are not yet supported on Windows Mobile.
Reviewed-by: Joerg
|
| |
| |
| |
| |
| |
| |
| |
| | |
A second worker function that was not defined in the descendant classes
was used in these cases. The missing worker functions have been
supplied and some tests skipped that depend on iterator ranges.
Reviewed-by: Joerg
|
| |
| |
| |
| | |
Reviewed-by: Olivier Goffart
|
|\ \
| | |
| | |
| | |
| | | |
Conflicts:
tests/auto/networkselftest/tst_networkselftest.cpp
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
firewall issue
Also check if we're not timing out instead of being able to fail.
|