| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\ |
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
CQtS60MainAppUi::HandleCommandL to the new QApplication::s60HandleCommandL
so that it is in QtGui rather than in the static app wrapper.
RevBy: axis
|
|/
|
|
|
|
|
|
|
|
|
|
| |
It was thought this test case was hanging earlier with Socks5Proxy,
but actually it was not hanging but just taking a lot of time to
complete. The reason for slowness was UDP packet fragmentation.
Without further studies I decided to decrease the written buffer size
for Symbian OS when using Socks5Proxy. This seems to solve the problems.
Also added some debug print why performance in Symbian OS is 0.00MB/s
without proxy.
|
| |
|
|
|
|
| |
code. Also, backgroundTexture is set in its own method, so there is no need to reset whole application palette when layout changes. Finally, some widget specific polishing corrections.
|
|\ |
|
| | |
|
| |\ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Made it more robust, as well as added support for the new
ImhDigitsOnly and ImhFormattedNumbers flags.
|
| | | |\ |
|
| | | | | |
|
| | | |/
| | |/| |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This was discussed with denis, and we found out that PIN codes on
phones are a use case where it would be an advantage to have digits
only. S60 already supports this mode of operation in their VK.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Only update the input context if it has already been created.
RevBy: denis
|
| | | |
| | | |
| | | |
| | | | |
RevBy: denis
|
| | |/
| | |
| | |
| | | |
RevBy: denis
|
| | |
| | |
| | |
| | | |
RevBy: denis
|
| | |
| | |
| | |
| | | |
RevBy: denis
|
| | |
| | |
| | |
| | |
| | | |
AutoTest: Included
RevBy: denis
|
| | |
| | |
| | |
| | | |
RevBy: Trustme
|
| | |
| | |
| | |
| | |
| | | |
AutoTest: Included
RevBy: denis
|
| | |
| | |
| | |
| | | |
RevBy: denis
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is meant to be used by widgets to signal that they want input.
The event will then be passed on to QInputContext::filterEvent, which
can create an appropriate virtual keyboard on devices with touch
interface only.
RevBy: denis
|
| |\ \ |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Need to study later on why performance is not as good as in other
platforms.
|
| |/ /
|/| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
I don't understand how socket->waitForDisconnected can work on other
platforms since socket->write will end to:
QMetaObject::invokeMethod(this, "_q_flushWriteBuffer", Qt::QueuedConnection);
In order that _q_flushWriteBuffer will be called the eventloop
need to run. If we just call waitForDisconnected, which blocks the
whole thread how that can happen? Changed the test for Symbian OS
to use evenloop since I'm not 100% sure. Probably this can change can
be applied for other platforms as well without changing the test case`
logic?
|
| | | |
|
|\ \ \
| |/ / |
|
| |\ \ |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This reverts commit 6df549b218e27c3fcc648d16bfc2aa1df7643b79.
This problem was fixed by commit 1a0fd473, so commit was possible to revert.
Task: 246600
Fix problem in eventdispatcher destructor / Active object canceling
|
| |/ /
|/| |
| | |
| | |
| | |
| | |
| | | |
This reverts commit 493f3e7691614dc12aaae75915ee7e988937e393.
The workaround is not needed anymore with Nokia X86 compiler
budled with Carbide C++ v2.x
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | | |
Task-number: 250632
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Put all variables in the same area for QDirectFBPaintEnginePrivate. Make
QDirectFBPaintEngine a friend.
Also, do away with setClipDirty and replace it with d->clipDirty = true;
Reviewed-by: TrustMe
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Move private functions to the bottom of the file to be more in line with
how most qt cpp files are structured.
Reviewed-by: TrustMe
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Make image caching a lot cleaner and more sensible.
By default we do not cache images since creating a preallocated surface
is quick and we don't really want to waste memory. In the case where the
driver does not support preallocated surfaces you can enable image
caching to speed up drawImage.
Reviewed-by: TrustMe
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Store whether qt was built with qt3support enabled in .qmake.cache. We
need this info to decide if QT3_SUPPORT should be defined when we
include qimage_p.h. Otherwise we get data corruption issues since the
size of struct in Qt is larger than the one we include in libqdirectfb.
Reviewed-by: Donald <qt-info@nokia.com>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Made SurfaceCache entirely inline for better readability.
Reviewed-by: TrustMe
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Store the memory address of our last QRasterBuffer::prepare() call to
make sure we reprepare if someone has unlocked and locked the device
behind our back.
Also optimize QDirectFBDevice::memory() since it might get called a fair
bit.
Reviewed-by: Donald <qt-info@nokia.com>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Fall back to raster engine when using a transform with
m11 < 0 || m22 < 0.
Task-number: 252921
Reviewed-by: Donald <qt-info@nokia.com>
|
| | | |
| | | |
| | | |
| | | | |
Reviewed-by: Paul
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Forward setDesktopBackground to setBackground as is mentioned in the
docs.
Reviewed-by: Paul
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
selections with different foreground but no background
The main concern is to avoid double painting. With anti-aliasing turned
on by default, we can not draw a piece of text on top of the same piece
of text without artefacts.
Task-number: 252310
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
the feature has to handle text with and without background, and extra
selections with and without background, or even only with underline style.
Trouble is that you sometimes want to accumulate styles, for example spell
checking wiggly underline plus search result highlights or background markup
from the css stylesheet.
Task-number: 252310
|