| Commit message (Collapse) | Author | Age | Files | Lines |
|\ |
|
| |
| |
| |
| |
| |
| | |
The path /lib/ld-linux.so.2 is correct for i386 only, possibly some
other archs. But on x86-64, it's usually ld-linux-x86-64.so and it can
be in either /lib or /lib64.
|
|\ \
| |/ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is mainly a stop-gap solution for 4.5.x. It trades painting performance
for correct painting.
Commit 7988d05da changed the opaque test from q->testAttribute(Qt::WA_OpaquePaintEvent)
to qt_widget_private(w)->isOpaque in qt_mac_update_widget_posisiton. This means
we'll do optimized moves in more cases. Unfortunately it also causes painting errors
in some cases (see the task).
Revert the commit for now to put the 4.5 branch in a god shape.
Task-number: 252295
Reviewed-by: nrc
|
| |
| |
| |
| |
| |
| |
| |
| | |
Line and polygon strokes did not respect the join/cap styles set
on a painter.
Task-number: 256914
Reviewed-by: Samuel
|
| |
| |
| |
| | |
QTest::touchEvent().
|
| |
| |
| |
| |
| | |
Fixes error:
src/gui/kernel/qevent_p.h:62: error: invalid use of incomplete type ‘struct QKeyEvent’
|
| |
| |
| |
| |
| | |
We now use QList/QVector over QHash. It is more efficient because most
of the time we iterate over the list of actions anyway.
|
| |
| |
| |
| | |
of calculation (ie. updateActionRects)
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
gcc 4.3 and 4.4 keep giving us a warning like:
'function()::type' declared with greater visibility than the type of
its field 'function()::type::subtype'
This seems to be a gcc bug. See the bug report for more information:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40145
|
| | |
|
| |
| |
| |
| |
| | |
These four enum values are used in variables of type Section, but aren't in it.
With gcc 4.4, it displays a warning that the value is lower than the lowest value
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
(ThreadEngineBarrier was implemented in the header as ThreadEngineSemaphore
in Qt 4.4 and Qt 4.5, and exported for a brief time in the Qt master branch. )
Unfortunately the inline call to acquire means that applications compiled
with Qt 4.4. and Qt 4.5 will contain a copy of the old implementation.
This is BC as long as the memory layout of the ThreadEngineBarrier class
stays the same, which means that we keep the QMutex member variable.
The old version of acquire will no longer be thread-safe since the new
version doesn't lock the mutex, but this is fortunately not a problem;
the only place it's called is in startAsynchronously() before the worker
threads are started.
|
|\ \ |
|
| | | |
|
|/ /
| |
| |
| |
| |
| |
| | |
Replace the SIZE constant with an Enum with a Qt-ish CamelCased name
(since SIZE conflicts with the system headers).
Reviewed-by: TrustMe
|
|\ \ |
|
| | | |
|
| | |
| | |
| | |
| | | |
We don't want to pull in too much if we can avoid it.
|
| | | |
|
|\ \ \
| |/ / |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
There's no need to have separate cast-checker functions, plus the cast-
and centralise the function to create the object.
Reviewed-by: TrustMe
|
| | |
| | |
| | |
| | |
| | | |
Only do that if the original event delivered to the QGraphicsView was
also spontaneous.
|
|\ \ \
| |/ / |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
These expressions aren't used anywhere yet, but I am sure we will find
use for them very soon now. I checked the compiler manuals for the
three commercial Unix compilers to verify which versions support these
macros.
Reviewed-by: Bradley T. Hughes
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If it was shared and you then set it back to an int type,
it is still marked as shared,. This might even lead to crashes.
The patch was sent through gitorious by Jürgen Starek.
Note: autotest added as well
|
| | | |
|
|\ \ \
| |/ / |
|
| |\ \
| | |/
| | |
| | |
| | |
| | |
| | | |
Conflicts:
src/3rdparty/webkit/VERSION
src/3rdparty/webkit/WebCore/ChangeLog
src/network/access/qnetworkreplyimpl.cpp
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Use the fully qualified classname at relevant places in the
moc-generated code. Also, QMetaObject::newInstance() needs to
strip the namespace part, since the constructor signatures
don't contain the fully qualified name.
Task-number: 246064
Reviewed-by: Simon Hausmann
|
| | |
| | |
| | |
| | | |
Reviewed-by: Trust Me
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
e65b4879116f4a8b0ee8b09607eef666c68c61d6 )
Changes in WebKit since the last update:
++ b/WebCore/ChangeLog
2009-06-25 Simon Hausmann <simon.hausmann@nokia.com>
Reviewed by and done with Tor Arne Vestbø.
Fix shortcut keyboard handling with plugins on the Qt/Mac build.
When we receive shortcut events like Ctrl+V then the text in the QKeyEvent is
empty. If we're asked to disambiguate the event into a Char keyboard event,
we try to detect this situation and still set the text, to ensure that the
general event handling sends a key press event after this disambiguation.
* platform/qt/PlatformKeyboardEventQt.cpp:
(WebCore::PlatformKeyboardEvent::disambiguateKeyDownEvent):
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This fixes a bug that occured together with a QProgressDialog.
The signal emission was like:
readyRead readyRead readyRead [...] readyRead finished readyRead
Now finished should be properly at the ending of this sequence.
Task-number: 256630
Reviewed-by: Thiago Macieira <thiago.macieira@nokia.com>
|
|\ \ \
| |/ / |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This significantly improves the support for
higher DPI-values on these platforms by
ensuring that common pixelmetrics are
scaled accordingly. In addition we mark all
Qt apps as DPI-aware on Windows 7 by calling
SetProcessDPIAware. We also changed the
way we draw pixmaps on the mac paintengine
when using dpi scaling > 1 to ensure smooth
pixmap scaling.
Reviewed-by: nrc
Task-id: 242417
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This change doesn't actually add public API for it, but makes it
trivial to add.
On the C++ side, qScriptConnect() would get an overload that
takes an additional argument, the connection type (d'oh, it
should have had a default argument to begin with!).
On the script side, it's a bit more tricky to "overload" the
existing connect(), since it's already "overloaded" (can have
either one or two parameters). Plus, I'd like connect() to be
able to support bind-like functionality so you can pass
additional arguments to it that will be passed to the signal
handler at signal emission time. Oh well, we'll see.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Change the QByteArray to a QRingBuffer to save re-allocation time.
Reviewed-by: Thiago Macieira <thiago.macieira@nokia.com>
|
| | |
| | |
| | |
| | | |
Task-number: 256918
|
| |\ \
| | |/
| | |
| | |
| | |
| | | |
Conflicts:
src/plugins/gfxdrivers/directfb/qdirectfbpaintengine.cpp
src/plugins/gfxdrivers/directfb/qdirectfbpixmap.cpp
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
enabled.
This allows mixing of debug and non-debug code (possible on Unix
systems) without causing assertion failures.
Reviewed-by: Bradley T. Hughes <bradley.hughes@nokia.com>
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
This bug made us call lock more than we needed to.
Reviewed-by: Donald <qt-info@nokia.com>
|
| | |
| | |
| | |
| | |
| | |
| | | |
Make sure surfaces always are locked when used as source for something.
Reviewed-by: TrustMe
|
| | |
| | |
| | |
| | | |
delete -> delete []
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The logic regarding whether or not a pen was simple was broken.
Essentially the pen is sonly simple if it should en up as a single pixel
line.
Reviewed-by: Donald <qt-info@nokia.com>
|
| | |
| | |
| | |
| | |
| | |
| | | |
Makes it work with custom message handlers (qInstallMsgHandler()).
Task-number: 233005
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
It's possible that the function gets called with a bytearray of
size -1 (for example, by QTextStreamPrivate::fillReadBuffer()).
Since the size was erroneously cast to a uint, the subsequent
comparison (arraySize > 3) succeeded and caused a crash.
Reviewed-by: Denis Dzyubenko
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Uncluttered and duplicated some function to make it more clear
what is happening. Was a bit confusing before if compressed data
or uncompressed data is handled.
Reviewed-by: Peter Hartmann
|