| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
- Get rid of double container lookups for conditional access.
- count() == 0 => isEmpty().
Reviewed-by: kh1
|
|
|
|
|
|
|
|
| |
After commit b881d8fb99972f1bd04ab4c84843cc8d43ddbeed, we would no
longer append "const" when seeing it after a *. This commit fixes the
regression.
Reviewed-by: ogoffart
|
|
|
|
|
|
|
|
|
|
| |
otherwise.
The documentation for flush() is that it flushes the outgoing command
queue on X11, but not when using Glib. Fix this by implementing flush()
in the GUI Glib dispatcher.
Task-number: QTBUG-3185
|
|
|
|
|
|
|
|
| |
Even though Qt doesn't support multiple displays, it is possible for
people to have code that uses multiple displays (either by using Xlib
directly or when integrating with another toolkit).
Task-number: QTBUG-3337
|
|
|
|
|
|
| |
Commit 9215506e6a057d8aef7415c2921214e1ba1c760d introduced one small
delta that would cause a certain example to stop working. This example
called update() from a paintEvent(), which now works again.
|
|
|
|
|
| |
GetMessageTime() is not available, so 9215506e6a057d8aef7415c2921214e1ba1c760d
is not possible on Windows CE
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
these functions just compare the d pointers of two objects. this can be
used to verify the validity of cached data: you keep a copy of the
original data in your cache. consequently, any changes to the original
data must detach, so this function reflects whether the cached data is
still up-to-date.
of course, this is not thread safe, as the data might change right after
you check it, but that's a general problem of cache coherency which
needs to be handled further up the stack.
the functions are internal because the other detaching-related functions
are internal as well for reasons beyond me.
Reviewed-by: brad
|
| | |
|
| |
| |
| |
| | |
Reviewed-by: kh1
|
| |
| |
| |
| |
| |
| | |
Added a QMacPasteboard converter for data dragged from the
address book on Mac. It is an easy piece of code, and will make it
easier for Mac people to work with standard Mac apps.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Avoid live-lock if native messages are generated quickly enough by
allowing posted events to be sent if more than 10ms has passed since
we last sent them. This means that we can allow multiple calls to
sendPostedEvents() during a single call to processEvents(), but only
when the QEventLoop::EventLoopExec flag is passed to processEvents().
Task-number: QTBUG-1697
|
|/
|
|
|
|
|
|
| |
If signalCount was 0, then indexOfSlotRelative would use -1 as the
lookup and read unitialized memory in the loop. This would cause a crash
in release on Windows.
Done-with: Olivier
|
|
|
|
|
|
|
|
|
|
| |
The QFileSystemWatcher signals the changing of a file several times,
with the first one coming too early. As a result, we are likely
checking a file that is not yet fully constructed.
The workaround/solution is to delay reacting to the change until
after the (hopefully) last signal from the QFileSystemWatcher.
Reviewed-by: kh1
|
|
|
|
|
|
|
|
|
| |
One of the reasons is that [NSView resetCursorRects] is called
for each view, also the ones not actually visible. And the
function is slow. This patch does an early check, and bails out
if this is the case.
Reviewed-by: Prasanth
|
|
|
|
|
|
|
|
|
| |
Also fixed it to use canonicalFilePath instead of absoluteFilePath since when
we get notification from the system, it gives us the canonical path with
resolved symlinks (for example when watching for /tmp, the notification that we
get says that /private/tmp was modified).
Reviewed-by: Prasanth
|
|
|
|
|
|
|
| |
Using FSRef to get a canonical file path on OS X 10.5 which doesn't support
realpath(X,0) extension.
Reviewed-by: Prasanth
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As far as we know realpath(X,0) extenstion is only supported on Linux, Mac OS X
starting with 10.6 and on Symbian.
Here goes the trick: realpath() on Mac properly handles file systems
case-sensitivity, meaning two files with different cases will are the same file
if the file system is case insensitive (which is the default on Mac). However
the QFSFileEngine will still say that the file system is case sensitive because
on Mac you can have several drives with different file systems (with different
case sensitivity), and QFSFileEngine doesn't allow to return different values
depending on the file path, so we still say that the file system is
case-sensitive, which is the safiest behavior.
This changes the behavior on Mac, but changes it to be correct.
Reviewed-by: Markus Goetz
Reviewed-by: João Abecasis
|
|
|
|
| |
Reviewed-by: kh1
|
|\ |
|
| |
| |
| |
| |
| | |
Task-number: QTBUG-3179
Reviewed-by: ogoffart
|
| |\ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Trying to fix QTBUG-6563, getting crash from cut-n-paste slippage, now fixed.
Task-number: QTBUG-6563
Reviewed-by: Rhys Weatherley
|
| | |
| | |
| | |
| | |
| | | |
Task-number: QTBUG-6574
Reviewed-by: Trust Me
|
| | |\ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
needed for building qtmobility and qtcreator docs without magic.
Reviewed-by: Daniel Molkentin
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Block changes in different selections happens quite frequently with
Qt Creator, e.g. when renaming local variables. The desired behaviour
which the tst_QTextCursor::cursorPositionWIthBLockUndoAndRedo() tests,
is like this: after an undo, the cursor should be where it was when
the block operation started. After a redo, the cursor should be
where it was after the block operation ended.
Reviewed-by: Simon Hausmann
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Block changes in different selections happens quite frequently with
Qt Creator, e.g. when renaming local variables. This test tests the
desired cursor position behaviour: after an undo, the cursor should be
where it was when the block operation started. After a redo, the cursor
should be where it was after the block operation ended.
|
| | | |
| | | |
| | | |
| | | | |
Reviewed-by: Olivier Goffart <ogoffart@trolltech.com>
|
| | |\ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Intel Q45/Q43 Express Chipset has problems with glColor4ub()
not updating GL_CURRENT_COLOR correctly. Replace all references
with calls to glColor4f() instead as it is more likely to be
implemented correctly on all chipsets.
Task-number: QTBUG-6217
Reviewed-by: Sarah Smith
|
| | |\ \ \ |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
During the exe(), sqlite does it's first stepping, and stores that into
the cache. It assumes that that value is still in the cache when fetchNext()
is called, and uses the "cached" value to return.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
readPiecewise() is assuming an empty valueCache when reading a new row.
setForwardOnly(true) means that only one row is used/re-used. The value
cache wasn't being cleared out when moving to a new row, so the above
assumption was invalid.
Task-number: QTBUG-6421
Reviewed-by: Justin McPherson
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
try first to lock without releasing the second mutex.
If it succees at first (likely), we should not have deadlock,
and we do not need to unlock and relock the first mutex
Should help in ~QObject
Reviewed-by: brad
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Avoid calling signalSlotMutex while there is a very small
probability that the node will be different or that the mutex
are the same for two different object.
Reviewed-by: brad
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Q_AUTOTEST_EXPORT is always defined.
(it is defined empty if not internal build)
Reviewed-by: Brad
|
|/ / / / /
| | | | |
| | | | |
| | | | | |
Reviewed-by: kh1
|
| | | | |
| | | | |
| | | | |
| | | | | |
Reviewed-by: kh1
|
| | | | |
| | | | |
| | | | |
| | | | | |
Reviewed-By: Thierry
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Merge-request: 391
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@nokia.com>
|
| | | | |
| | | | |
| | | | |
| | | | | |
Reviewed-by: kh1
|
| | | | |
| | | | |
| | | | |
| | | | | |
Reviewed-by: kh1
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Calling [NSView addTrackingArea] is slow. So doing this for
views that are not even visible on screen is unnecesary. This
patch will greatly improve the speed for some (perhaps extreme)
cases.
Task-number: QT-1610
Reviewed-by: MortenS
|
| | | | | |
|
|\ \ \ \ \
| | |/ / /
| |/| | | |
|
| |\ \ \ \
| | | | | |
| | | | | |
| | | | | | |
oslo-staging-1/4.6 into 4.6
|
| | |\ \ \ \ |
|