| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Gesture types are now separated to internal ones, which are listed as
enums (though they might be converted to strings internally), and
third party gestures which are referenced by strings.
From now on QGesture objects derive from QObject, which means third
party gesture recognizer developers can use QObjects property system
to store custom data inside QGesture without need to subclass it.
Some functions were renamed to show their purpose more clear.
|
|
|
|
|
| |
QGraphicsSceneGestureEvent to a viewport, so that the user could
subscribe to gestures in a viewport as well.
|
|
|
|
|
| |
providing some additional info (like a widget that received a gesture
- for coordinates conversions).
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
gesture manager should consume it as well.
|
|
|
|
|
|
| |
Details: Several fixes - parsing only spontaneous mouse events and
send gesture events to QGraphicsSceneItems according to their
z-order
|
|
|
|
|
|
|
| |
events.
Details: Copying the QEvent::spontaneous() flag from the received
event to QGraphicsSceneEvent.
|
|
|
|
| |
finished.
|
|
|
|
| |
Fixed missing const specifiers.
|
| |
|
|
|
|
|
| |
This is a squashed merge of all of the changes in the maemo-gestures
branch on-top of the qt/4.5.0 branch.
|
|\ |
|
| |\
| | |
| | |
| | | |
windows-7-multitouch
|
|\ \ \
| |/ /
|/| /
| |/ |
|
| |
| |
| |
| |
| |
| | |
- partly revert f0243e70e05a3368582fd0478d840096d6b60c3f as it broke the build due to widgets accessible plugins using QDockWidgetLayout
Reviewed-by: Rhys Weatherley
|
| | |
|
| |
| |
| |
| | |
Reviewed-by: ogoffart
|
| |
| |
| |
| | |
Reviewed-by: ogoffart
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
no more exported
designer was using QToolBarLayout members. We fixed that by using
styles.
Reviewed-by: Friedemann Kleint
Reviewed-by: ogoffart
|
| |
| |
| |
| |
| |
| | |
In the past, we checked on the existence of the pointer, but now that
this is controlled by the property, we need to also check the pointer in
the action event.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
With this patch, commands no longer merge across block bounderies.
In order to have merging still work for the normal insertion and deletion
case, the unnecessary beginEditBlock()/endEditBlock() calls where
cleaned up.
Reviewed-by: Simon Hausmann
|
| |
| |
| |
| | |
This new test tests desired undo merging behaviour after insertions.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
It seems that plugins were never explicitly unloaded, resulting in leaks
of the instance object. Added a static deleter to ensure deletion on
exit. The QPointer (previously in place) ensures we don't do a
double-free nor try to access an invalid pointer.
Task-number: 253013
Reviewed-by: mariusSO
|
| |
| |
| |
| |
| |
| |
| | |
Static variable was dynamically allocated but never freed.
Task-number: 253013
Reviewed-by: Thiago
|
| |
| |
| |
| | |
Reviewed-by: Thorbjørn
|
| | |
|
| |
| |
| |
| | |
just needed to add multitouch to SUBDIRS in examples/examples.pro
|
| |
| |
| |
| | |
this makes sure we always get touch events, and the don't drop out seemingly randomly.
|
| |
| |
| |
| |
| |
| | |
the finger may not move, meaning no update with move event is generated,
even if we say "press, hold, release" when testing (the finger may not
wobble enough)
|
| | |
|
| |
| |
| |
| |
| | |
the only thing we store in the QWidgetPrivate is the current touch point
list, nothing more (the rest is local state in the event translation code)
|
|\ \
| |/
| |
| | |
windows-7-multitouch
|
| |
| |
| |
| |
| |
| | |
Qt itself was O2 from 4.2 and up, this changes it for applications as well.
Reviewed-by: nrc
|
| |
| |
| |
| | |
Reviewed-by: thartman
|
| |\
| | |
| | |
| | |
| | |
| | | |
Conflicts:
src/gui/painting/qbackingstore.cpp
src/gui/painting/qwindowsurface_raster.cpp
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When passing a printer that is set up to print to a PDF file into
QPrintDialog, the print dialog could invalidate the printer and
not update the validity of it in a proper manner.
Task-number: 252873
Reviewed-by: Samuel
|
| | |
| | |
| | |
| | | |
Reviewed-by: TrustMe
|
| | |
| | |
| | |
| | | |
Reviewed-by: nrc
|
| | |
| | |
| | |
| | |
| | |
| | | |
Added two missing types to the list.
Task-number: 252274
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We must tell the system that we want to intercept the back key on
Windows mobile. Each toplevel widget that needs correct back key
behaviour needs to have a menu bar. Why? Ask Microsoft...
Task-number: 248846
Reviewed-by: thartman
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The fix for 1x1 source rect image drawing in change
ffbb3c1a2aee4134dce80cd144a26bf32865b698 was incorrect for transforms
with type >= TxScale. The aliased coordinate delta needs to be applied
in device coordinates, not in logical coordinates.
Also specialize the non-antialiased TxScale case by simply calling
fillRect_normalized directly, avoiding having to scan convert the
rectangle manually.
Task-number: 251561
Reviewed-by: Trond
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
original patch by Benjamin Meyer.
Handle multiple cookies split by new lines in a cleaner way.
Parsing the combined string was error prone. Splitting them and
sending each line through our header parser is more robust, and has
more obvious code paths.
Tested by logging into wordpress.com, facebook.com etc.
Reviewed-by: Thiago
Task-number: 251959
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Updates triggered by the line edit itself, i.e. cursor blinking, are not
processed after the top-level is resized. This is yet another problem
caused by the event dispatcher on Windows (Qt posted events are not sent
during top-level resize, task 146849). We added a work-around for that
particular case by posting an event via Windows, but the widget is not
visible on the screen (hidden from Windows' POV) so it'll never be posted.
And of course then we'll never receive it and the backing store is not
synced. This work-around is therefore useless for widgets that are
not visible on the screen.
However, not receiving update requests while resizing the top-level
(in this case QGraphicsView), is not a problem for embedded widgets
because all items and hence the proxied widgets are repainted by
graphics view anyways.
Task-number: 252400
Reviewed-by: Olivier
|