| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
| |
This is a big change from the original,
and I expect we will want modifications.
|
|
|
|
|
|
|
| |
Events caused by dragging a mouse are currently unavailable in
Windows Mobile.
Reviewed-by: Joerg
|
|
|
|
|
|
|
|
|
|
|
| |
Incorrect optimisation - for popup windows, Qt's focus is moved before
hide_sys is called, resulting in the popup window keeping its elevated
position in the CONE control stack.
This can result in keyboard focus being in an invisible widget in some
conditions - e.g. QTBUG-4733
Task-number: QTBUG-4733
Reviewed-by: axis
|
|
|
|
|
|
|
|
|
|
| |
Not exporting the whole class prevents the capabilities example from
linking, because the vtable is not exported.
However windows builds don't support export of templated class, and
export the vtable implicitly when there is an exported member function.
Task-number: QTBUG-4593
Reviewed-by: Thierry Bastian
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
It turns out that scrolling appears to be slow when using
non-mac mice with the carbon build. This patch introduces a
an acceleration algorithm that closer resembles the one
used by Cocoa.
Rev-By: prasanth
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
...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
|
| |
| |
| |
| |
| |
| | |
This reverts commit c15b370c9db16fdbfd9e7bec89ee9bf8c1110827 since it is
causing a problem with the autotests so that will be investigated further
before this is resubmitted.
|
| |\ |
|
| | |
| | |
| | |
| | |
| | |
| | | |
Added the missing defines
Reviewed-by: Denis
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Changing names to Symbian platform
Task-number: QT-2268
Rev-by: Espen Riskedal
|
| |/
| |
| |
| |
| |
| |
| |
| | |
Changing names to Symbian platform
Task-number: QT-2268
Rev-by: Espen Riskedal
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The reason for scrolling bug was that CFbsBitmapDevice wasn't
informed if CFbsBitmap was resized. However, it seems that
scroll implementation in QRasterPixmapData is faster that
CFbsBitGc->CopyRect so this is also a patch which changes
QS60PixmapData's scroll function to call QRasterPixmapData::scroll().
Reviewed-by: Janne Koskinen
|
| |
| |
| |
| |
| |
| |
| | |
This restores the behavior in 4.5.
Task: QT-2257
RevBy: Simon Hausmann
|
| |
| |
| |
| | |
Reviewed-by: TrustMe
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
OpenC incorrectly caches DST information between localtime_r
calls, i.e. if previous call to localtime_r has been called for DST
affected date, also the second call will be affected by DST even
the date is such that DST should not be applied.
The workaround is to call mktime with non-DST affected date before
calling localtime_r. mktime call resets the OpenC internal DST cache
to right value and localtime_r will return correct values.
This commit can be reverted once Open C bug 9525 has been reverted.
AutoTest: Fixes tst_QDateTime::totime_t
Reviewed-by: Aleksandar Sasha Babic
|
| |\ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This code was kind of dead anyway because
- On X11 and Windows, most of the widgets have the StrongFocus FocusPolicy
- On Mac, e->modifiers always contains KeypadModifier for arrows, so the
code is never reached on mac with real applications
Morever, QAbstractButton already have a more complex handling of arrow keys.
And the code breaks the QButtonGroup arrowKeyNavigation test on Mac (as when
the test system simulates events, the KeyPadModifier is not set)
Reviewed-by: mbm
Reviewed-by: Paul
|
| | |
| | |
| | |
| | | |
Reviewed-by: Jens Bache-Wiig
|
| | |
| | |
| | |
| | |
| | | |
Add Q_ENUMS/Q_FLAGS accordingly.
Reviewed-by: Olivier Goffart <ogoffart@trolltech.com>
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This fixes issue that both DialogButtonBox and softkeys are visible
(e.g. in Ftp example) at the same time.
Reason is that the previous implementation did the visiblitity setting when buttons were created.
Unfortunately buttons can be created without parent and let layout manager to find parent them
for you - so dialog as parent (=hide dialogbuttonbox as softkeys are in use) check failed.
Now similar check is done before showing the widget - it is layoutted here, so it has parent as well.
As a bonus, the event handling is already looking for dialog parent, so we can avoid doing another
for-loop.
Task-number: QTBUG-4739
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When processing a project in a subdirs template failed for whatever
reason then qmake would lose the result of that and would return an
error code of 0 if the subdirs project file itself was processed fine.
So now it ensures that any errors arising from processing a project
referenced in a subdirs project file are not lost so that the error code
returned from qmake will indicate an error actually occured.
Task-number: QTBUG-4065
Reviewed-by: mariusSO
|
| |
| |
| |
| |
| |
| | |
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
|
|
|
|
|
|
|
|
| |
The error was: "*** No rule to make target `\Qt\tests\auto\kernel\
qguiplatformplugin_p.h_, needed by ..." This happens since Symbian does
not use same include semantics.
Reviewed-by: Miikka Heikkinen
|
|
|
|
| |
Reviewed-by: Miikka Heikkinen
|
|
|
|
| |
Reviewed-by: TrustMe
|
|
|
|
| |
Reviewed-by: TrustMe
|
|
|
|
|
|
|
|
|
|
| |
When QGLWidget was used as a viewport for QGraphicsView on PowerVR/MBX
systems, it was double-flushing every frame because the window surface
flush() implementation was still trying to do a raster blit after painting.
This change suppresses the raster blit, leaving it up to the GL
swapBuffers() call to get the painted contents onto the screen.
Reviewed-by: Sarah Smith
|
|
|
|
| |
Reviewed-by: TrustMe
|
|\ |
|
| |
| |
| |
| |
| | |
It's faster than calling getObject(), since getObject() will do
type checking of the value.
|
| |
| |
| |
| | |
Make allocation faster.
|
| |
| |
| |
| |
| |
| | |
There's no CSIDL_LOCAL_APPDATA on Windows CE. Use CSIDL_APPDATA instead.
Reviewed-by: TrustMe
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Making the triangle fan of each sub path start at the sub path's
centroid will on average improve performance for complex paths, because
less pixels that are outside the path need to be touched. The centroid
is a more balanced choice than just picking the first element of the
sub path as triangle fan origin.
A performance improvement of 20 % was measured for star formed paths.
Reviewed-by: Trond
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When no stencil clip is set we reduce the number of compositing passes
for rendering winding fill paths from four to two. When stencil clip is
set, the number of compositing passes is reduced from five to four.
For clipping with a winding fill path, the number of compositing passes
are reduced from five to four when stencil clipping is already enabled.
A performance improvement of up to 85 % was measured in certain cases.
Reviewed-by: Trond
|
| |
| |
| |
| |
| |
| | |
This might be useful for some people, so we should document it.
Reviewed-by: Bjørn Erik Nilsen
|
|/
|
|
|
| |
This reverts commit 342fcb287b09d016d482e25482ddd1b36e2983a3.
Didn't work on all compilers
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add a backend for QFileIconProvider in the platform plugin
Also change the QIcon::fromTheme backend in the platform plugin:
On KDE, we unfortunately can't use KIcon as backend, as the current
API doesn't let us know easily (and quickly) wether we should use
the fallback or not (KDE always fallback to the question mark
"unknown" icon)
So we will use the QIconLoader even on KDE.
But we need to make sure that the theme name and the icon search paths
are correct. Ask that to the platform plugin
Reviewed-by: Jens Bache-Wiig
|
|
|
|
|
|
|
| |
Make tst_QTextLayout::testTabDPIScale work by increasing the tab
stop distances. Now, systems with higher DPIs can pass this test.
Review-By: Joerg Bornemann
|
|
|
|
| |
Reviewed-by: Olivier
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
This reverts commit bf8d74bb8e849cb9eea74ef8fdb82d8926c48880.
Breaks more cases than it actually fixes.
modified: tests/auto/qtextlayout/tst_qtextlayout.cpp
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
version for development.
This used to work before 4.5.1
Task-number:Qt-704
Reviewed-by:thiago
|
|/
|
|
|
|
|
|
| |
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 should not create a QAction instance at program startup,
that is before QApplication was initialized. One reason not
to do that is that internal fonts are prematurely initialized
without QApplication::qt_is_gui_used set to true, which leads
to wrong font Dpis in qt_defaultDpiX().
This issue was detected due to the failure in tst_QTextLayout,
cases: testDefaultTabs, testTabs, testMultilineTab,
testRightTab, testTabsInAlignedParag, testCenteredTab,
testDelimiterTab, testMultiTab and tabsForRtl.
Fix: create a Q_GLOBAL_STATIC_WITH_ARGS for that QAction
instance.
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
|