| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
it is simpler to keep it in sync with creator then.
|
| |
|
|
|
|
|
|
|
|
|
| |
In some cases, weird timing issues could occur. In those cases, an EOF
was sent twice for the upload data, leading to the HTTP code being
confused and sending the request headers twice.
Task-number: 257662
Reviewed-by: Thiago Macieira
|
|
|
|
|
|
|
|
| |
Brought up by Andy. See perforce change 314809,
17b07e3ab6192b31f77fd2f126705b9ab53b3937. Related to task 221708.
Reviewed-By: Andy Shaw
(cherry picked from commit cc24c46c117248ecb98200416e7f25375e6bb476)
|
| |
|
|
|
|
|
|
|
| |
Fixes an issue where too many parameters are bound when updating
QSqlTableModel where the stored record has NULLs in it.
Reviewed-by: Justin McPherson
|
|
|
|
| |
cherry-picked 07730341bd739aac823ac9b4336d8294510a35e2 from creator
|
|
|
|
| |
cherry-picked 167a09b20614d282ec898f69fc2a3f0bafa11229 from creator
|
|
|
|
| |
cherry-picked d8b1cc5f0ecbb8de734d241d72a05b325c2bbb2c from creator
|
|
|
|
|
|
|
|
|
| |
The inputContext's focusWidget was not reset when disabling input
methods.
Thanks to Benjamin P.
Task-number: 257832
Reviewed-by: Denis
|
|
|
|
| |
... so it works under windows as well.
|
|
|
|
| |
use absolute paths for the tested executables
|
|
|
|
|
|
|
|
|
| |
Until this fix very few cases of drawTiledPixmap and
fillRect(r, textureBrush) have been handled by DirectFB.
This patch makes it possible to accelerate such operations.
Reviewed-By: Donald <qt-info@nokia.com>
|
|
|
|
| |
Reviewed-by: Friedemann Kleint
|
|
|
|
|
|
|
|
|
|
| |
Kind of like f37bd111f7622a34b3a7bd63f5a82f6042dc0f0d, but the real
thing. The widget box wasn't showing on Linux when switching to
top-level mode. Incidentally, this was the main window there...
Reviewed-by: Friedemann Kleint
After some persuasion the Cat also came to see things this way.
|
|
|
|
| |
Reviewed-by: Peter Hartmann
|
|
|
|
|
|
|
| |
We didn't use to pass the device in to the keyboard handlers rendering
them mostly useless.
Reviewed-by: TrustMe
|
|
|
|
| |
Task-number:207874
|
|
|
|
|
|
|
| |
Call PQclear() regardless of the status of the result returned by
PQexec().
Reviewed-by: Bill King
|
| |
|
|
|
|
|
|
|
|
| |
We cannot assume the position of the decorations when a QGroupBox get
the focus.
Task-number: 257660
Reviewed-by: Thierry
|
|
|
|
| |
Task-number: 256647
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
- postgreSQL specific autotest.
Task-number:233829
|
|
|
|
|
|
|
|
|
| |
When contructing the EXECUTE statement, there is a special case that
we need to handle whereby we explicitly put quotes around the
special float values before submutting the statement for execution
Task-number:233829
Reviewed-by: Bill King
|
|
|
|
|
|
|
|
|
| |
We've had this since 4.5 and it's very annoying to see the window show
and quickly hide itself. I was hoping it wasn't a bug in Qt, and it
turns it isn't and it was happening on all platforms.
Reviewed-by: Friedemann Kleint
Shout outs: João for testing.
|
|
|
|
|
|
|
|
|
|
| |
It seems there is a bug in AppKit which will automatically reset a
cursor even when it is grabbed, but won't reset it when it's brought
back into the window. The upshot of this is that doing a setCursor()
inside of mouse handling behaves slightly different than on the other
platforms (including Carbon). However, we are at the mercy of Cocoa here
and I would rather have all the other things AppKit does right and live
with this bug which they may fix some day.
|
|
|
|
|
|
|
|
|
| |
Argh! It's divide by 256 not 265. The worst part was that I used the
same values in Cocoa as well, so they were both "damaged." It should be
good now.
Task-number: 257499
Reviewed-by: Prasanth Ullattil
|
|
|
|
|
| |
Task-number: 257247
Reviewed-by: trustme
|
|
|
|
|
| |
Merge-request: 803
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@nokia.com>
|
|
|
|
|
| |
Merge-request: 803
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@nokia.com>
|
|
|
|
|
| |
Merge-request: 803
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@nokia.com>
|
|
|
|
|
| |
Merge-request: 803
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@nokia.com>
|
|
|
|
|
| |
Merge-request: 803
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@nokia.com>
|
|
|
|
|
|
|
|
|
| |
typo fixes;
clarify several strings;
use 'own languages' hack
Merge-request: 803
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@nokia.com>
|
|
|
|
|
|
|
| |
almost done; only few strings left untranslated.
Merge-request: 803
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@nokia.com>
|
|
|
|
|
| |
Merge-request: 803
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@nokia.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
OK. this is a bit strange. It seems the topdata->resizer value is used
to control whether or not we should show a resize handle based on a
count (0 no, non-zero yes). Since we somehow decided that this value
will never be larger than 15, we made it 4-bits wide. There's a "Qt/Mac"
API, QWidgetPrivate::qt_mac_update_sizer(QWidget *, int = 0) which
would adjust this value by the int passed in.. We use that in several places, not excluding
the QStatusBar where we would pass 1 if we want to show, and -1 if we
didn't. Now if you subtract -1 from zero when you are 4 bits wide, well,
bad things happen. Therefore protect that (since if it's at zero we have
succeeded, we don't want to show the resizer). This seems to work well.
The private API is certainly an interesting way of solving the problem,
but is easy to abuse (for example, this code will break if resizer = 1
and we are passed -2 in the function.
Task-number: 257485
Reviewed-by: Prasanth Ullattil
|
|
|
|
|
|
|
|
|
|
|
| |
Seems this was a victim of our cursor fixing. Cocoa does a lot for us
with setting cursors. This meant that we didn't need to do as much
meddling and as a result qt_mac_set_cursor does nothing in Cocoa.
Unfortunately, this broke setOverrideCursor. Luckily Cocoa has a stack
that works exactly like Qt, so we can just use that.
Task-number: 257507
Reviewed-by: Prasanth Ullattil
|
|
|
|
| |
Reviewed-by: kh
|
|
|
|
|
| |
Task-number: 257441
Reviewed-by: kh
|
|
|
|
|
|
| |
Sql server fails at numeric field calculations. (Confirmed by running
against MySql via odbc). Also, quote fields properly. The drivers know
how to do it correctly, so let them handle it.
|
|
|
|
|
| |
Sql Server can't count. Reduce the expected length of string when we're
on sql server.
|
|
|
|
|
|
|
|
| |
Looks like this `&&' was meant to be `||'.
QNetworkProxy::FtpCachingProxy is 5 so it's clearly impossible for type
to be less than 0 and greater than QNetworkProxy::FtpCachingProxy.
Reviewed-by: Aaron Kennedy
|
| |
|