| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
basically reordering members initialization in constructors or fixing
singed/unsigned checks.
Reviewed-by: Trustme
|
| |
|
|
|
|
|
| |
Autotest: included
Merge-request: 378
Reviewed-by: Eskil Abrahamsen Blomfeldt <eblomfel@trolltech.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This makes Qt work on VxWorks 6.6+ in native (kernel) mode.
* compiles with the WindRiver GNU toolchain (Linux only)
* works with QWS (tested with the VNC driver only)
* tested on PPC hardware and the x86 VxWorks simulator
* no q3support, no phonon, no webkit
* no QSharedMemory, no QSystemSemaphore, no QProcess
* only one QApplication instance (flat address space)
* filesystem support depends heavily on the quality of the native driver
* QLibrary is just a dummy to make plugins work at all
* qmake transparently creates VxWorks munching rules for static ctors
* made auto-test cope with missing OS features
A special note regarding the Q_FOREACH patch for dcc:
when calling foreach(a,c) with c being a function returning a container,
the compiler would generate 5 references to some labels (.LXXXX), which
are not there (so the linker complains in the end).
Seems like dcc doesn't really like the 'true ? 0 : <function call to get type>'
statement
Reviewed-By: Harald Fernengel
|
| |
|
|
|
|
|
|
|
|
|
| |
The problem was that on Windows, we would activate on WM_LButtonUp,
but a double click after activating will also generate a second
WM_LButtonUp. Hence we get three activations. The fix was basically
to filter out the second WM_LButtonUP, something we also do in
qapplication_win.cpp.
Task-number: 205499
Reviewed-by: denis
|
| | |
|
| |
|
|
|
|
|
|
|
| |
OpenUrl couldn't open relative urls because we were passing 'file:///'
schema to the ShellExecute on Windows
Reviewed-by: Prasanth Ullattil
# with '#' will be ignored, and an empty message aborts the commit.
|
| |
|
|
|
| |
Merge-request: 884
Reviewed-by: Olivier Goffart <ogoffart@trolltech.com>
|
| |
|
|
|
|
|
|
| |
This is Windows CE only. For Windows mobile we don't support context
menus for system tray icons.
Task-number: 250528
Reviewed-by: thartman
|
| |
|
|
|
| |
we should include qt_windows.h and not windows.h because we have to
define WINVER to 0x500.
|
| |
|
|
|
|
| |
Merge-request: 653
Reviewed-by: Olivier Goffart <ogoffart@trolltech.com>
Task-number: 247560
|
| | |
|
| |\
| |
| |
| |
| | |
Conflicts:
src/network/socket/qlocalsocket.cpp
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Also - Make winPeekMessage() & winPostMessage() obsolete
- FlashWindowEx, IsValidLanguageGroup functions no longer resolved
dynamically (available on >= Windows 2000)
- LoadIcon/LoadCursor -> LoadImage w/LR_SHARED for system
icons/cursors
- qsystemtrayicon_win: use Shell_NotifyIconGetRect if available
(Windows 7)
Merge-request: 604
Reviewed-by: Marius Storm-Olsen <marius@trolltech.com>
|
| |/
|
|
|
| |
Task-number: 256138
Reviewed-by: jasplin
|
| |\
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
src/3rdparty/webkit/VERSION
src/3rdparty/webkit/WebCore/ChangeLog
src/3rdparty/webkit/WebKit/qt/ChangeLog
tests/auto/qgraphicsitem/tst_qgraphicsitem.cpp
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
After discussing with some of the Objective-C
people I have finally got a fair number of the
warnings to disappear in both 10.5 and 10.6. I
also took the opportunity to remove a bunch of
other warnings.
Reviewed by: Morten Sørvig
|
| |\ \
| |/ |
|
| | |
| |
| |
| | |
Reviewed-by: Trust Me
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
It turns out that the fix 7bf4512659113f8cc78e72f1c84158ce4f70a526
caused the QCompleter popup from appearing for a split second on
Windows. This is because the popup is shown as a toplevel window
on this platform. On other platforms than Mac and Windows it doesn't
seem to matter, but be on the safe side, the fix is modified to
apply for Mac only.
Reviewed-by: Daniel Molkentin
Task-number: 255374
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
On Mac, a new completer popup must initially have its show()
method called rather than its hide() method. Otherwise the event
handling done by the completer results in a bad state.
On other platforms it doesn't matter.
Reviewed-by: Richard Moe Gustavsen
Task-number: 255374
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
QDestopServices was converting the file names to percentage encoding
before calling ShellExecute. This will not work with URLs without a
scheme. These are now being treated similar to a file.
Task-number: 254501
Reviewed-by: Jens Bache-Wiig
|
| | |
| |
| |
| |
| |
| |
| | |
This compiler doesn't seem to follow the same rule as others
for implicit conversions to/from wchar_t.
Add the necessary casts, keeping in mind that sizeof(wchar_t) == 2
on Windows.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Thunderbird sets only the user level shell association for mailto. This
is now being read before the default mail application registry.
The registry crawling could have been avoided by using the ShellExecute()
but it supports only around 2KBytes of data as parameter, so we will
continue using CreateProcess().
Task-number: 251554
Reviewed-by: Jens Bache-Wiig
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In the past, TempLocation would return something like:
/private/var/folders/4k/4k97GBy2Ha46D3DAWSLbQE+++TI/TemporaryItems
Now it returns something like:
/var/folders/4k/4k97GBy2Ha46D3DAWSLbQE+++TI/-Tmp-
This isn't that different and it's a temporary location so it shouldn't
effect many people (and it will be gone once the system reboots anyway),
but the issue could be that TemporaryItems isn't there and that it's a
bit more "Carbon" to use TemporaryItems. Also our own documentation
claims they are equivalent and I'm happy to do that.
I also enforced the Qt-style of if-statements and got rid of the extra
qualifiers to make the code look nicer.
Task-number: 253806
Reviewed-by: Morten Sørvig
|
| | |
| |
| |
| |
| | |
used character operations whenever possible
better usage of QLatin1String
|
| | |
| |
| |
| |
| |
| |
| | |
Wherever I found that we were using a string instead of a single char
I fixed the code.
Reviewed-by: olivier
|
| |\ \
| |/ |
|
| | |
| |
| |
| |
| |
| | |
Usually, "the the" is not proper English
Reviewed-By: Thiago Macieira
|
| |\ \
| |/ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fixes regression introduced in a794ded85f74516239a08cf848e6b4f8b6dcac6a.
When using UnfilteredPopupCompletion the matchCount is always zero and
completion was being skipped. By adding the check for showAll we still
avoid the assert but retain correct behavior.
Task-number: 253125
Reviewed-by: jasplin
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Task-number: 246130
Reviewed-by: joerg
Introduce Q_WS_WINCE for Windows CE only windowing parts. So far we
decided to stick with Q_WS_WIN32, but having a separate define
makes the code more readable. In addition Q_WS_WINCE_WM is available
for Windows Mobile only parts, where we do not check for the OS on
runtime.
|
| |\ \
| |/
| |
| |
| | |
Conflicts:
tests/auto/qaction/tst_qaction.cpp
|
| | |
| |
| |
| | |
Reviewed-by: TrustMe
|
| |\ \
| |/ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Commit 4a00810cc394b7da99ddb2d13eb045352ede25d3 ensures
that setting the focus policy of a widget applies to its
proxy (if any) as well. This propagation effect is however
unfortunate for a QCompleter in PopupCompletion mode.
The client widget (typically a QLineEdit or a QTextEdit)
acts as the focus proxy to the popup menu. Internally,
the completer sets the focus policy of the popup menu to
NoFocus, but this should not affect the focus policy of
the editor.
Reviewed-by: janarve
Task-number: 250064
|
| |\ \
| |/
| |
| |
| | |
Conflicts:
src/gui/inputmethod/qximinputcontext_x11.cpp
|
| | |
| |
| |
| |
| | |
Task-number: 223087
Reviewed-by: TrustMe
|
| |\ \
| |/ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Calling setCompletionPrefix() on a QCompleter from a slot connected
to the editingFinished() signal of the corresponding QLineEdit
could in some cases alter the internal state of the completer in
such a way that an assertion would fail. The fix prevents the
asserting code from being called in this particular state.
Reviewed-by: janarve
Task-number: 246056
|
| | |
|
| |
|
