| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
Most Wacom tablet have a coordinate origin at 0 (Bamboo,Intous), but
some tablet (like DTF 720, which have an integrated screen) have a non
zero coordinate origin. Which lead to an errounous y/a tablet pos
reported by Qt tablet event.
Merge-request: 822
Reviewed-by: Norwegian Rock Cat <qt-info@nokia.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Basically if you would hide a toolbar in the unified toolbar, you
would still see a little bit of area at the top instead of having
everything flush with the titlebar. This change basically unsures that
the unified toolbar makes a decision to hide itself if all the toolbars
inside it are hidden. It makes the behavior of clicking on the toolbar
button behave more or less correctly since we are going to show the
unified toolbar whether we want to or not.
This all will get the toolbar button switch event to be dispatched in
Cocoa as well.
Also add an optimization for checking if we need to change the geometry.
If we don't have any items the other toolbar areas, we can skip the set
geometry call, which wrecks havoc with things in Cocoa.
We still don't solve the case of someone who has hidden the items with
the toolbar button then goes full-screen, then goes back out. I'm not
motivated to solve it as is because we need to keep track of the
hides we do on the button press vs. other hides from the user and still
people can workaround it easy enough by handling window state change and
doing what is recommended in the docs.
Task-number: 208439
Rev-by: Denis
|
|
|
|
|
|
|
|
|
| |
Write only local sockets silently disconnected after some time.
Reason: we cannot call PeekNamedPipe on a write only pipe.
Task-number: 257714
Reviewed-by: ossi
Autotest: tst_QLocalSocket::writeOnlySocket
|
|
|
|
| |
Reviewed-by: Thierry
|
| |
|
| |
|
|
|
|
| |
QTimeLine is now no more used in private APIs
|
|
|
|
| |
Reviewed-by: TrustMe
|
|
|
|
| |
Reviewed-by: trustme
|
| |
|
|
|
|
| |
currentChange is slot in the public class (QAbstractItemView
|
| |
|
|
|
|
| |
Task-number: 189232
|
|
|
|
|
|
|
| |
This partially reverts 9a5b40a011bd1b15a67d83564af55011761f8ad9 for
the QIconvCodec.
Reviewed-by: hjk
|
|
|
|
|
|
|
|
| |
When the parsing of an SVG attribute fails, it should be given the
default value. Fixed handling of invalid viewBox, stop-opacity and
stop-offset. Autotest included.
Reviewed-by: Kim
|
|
|
|
|
|
|
| |
Fixed inheritence of fill-opacity, fill-rule and fill. Autotest
included.
Reviewed-by: Kim
|
|
|
|
|
|
| |
Cache return value of expensive function.
Reviewed-by: Peter Hartmann
|
|
|
|
| |
make compiler distinguishing both happy.
|
|
|
|
| |
Task-number: 189232
|
| |
|
|
|
|
|
| |
On the font from the font dialog, we can only test family, size and
style
|
|\ |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
qdoc reported an error if you used \section2 on its owin,
i.e. with no outer \section1. While strictly speaking
correct, it imposed an unnecessary restriction,
e.g. sometimes you just want to use \section2 to get a
smaller title for a section.
|
| | |
|
|/
|
|
|
| |
Triggered on Designer startup on Linux.
Acked-by: Thierry Bastian <thierry.bastian@nokia.com>
|
|
|
|
|
|
|
|
|
|
|
| |
Now, if you try to run an unsigned test on a locked device,
you'll get:
"Error invoking qRemoteLaunch on \Windows\QtRemote.dll: Invalid Signature. (0x80090006)"
Instead of what you would previously get:
"Error: Could not execute target file"
|
|
|
|
|
|
|
|
|
| |
Includes:
9b532a999944c70c2e8f57d9156c1887867ad9f1 - qtlibinfix
bb8e25a5074a378d5003577fefbeabb1de846a81 - cetest fix
5ea86cfac34f65b2321ceeeb651e4e7099bf59a0 - QT_WA removal
349997b5c4167b07d0bdc55beff175b39f3abe75 - spelling fix
bae8bc5d23946036b2c1079fc6f1b3bceeaa19ca - QT_CONFIG+=private_tests
|
|
|
|
|
|
|
|
|
|
|
|
| |
-developer-build, part 2.
Some autotests use private (unexported) code, either because they're
testing private classes or because that's the easiest way to test
the public classes. Configuring Qt with `-developer-build' is needed
for these tests.
This commit fixes the tests so configuring without `-developer-build'
only builds the tests which strictly use public API.
|
|
|
|
|
|
|
|
|
| |
-developer-build, part 1.
Adds QT_CONFIG+=private_tests to qconfig.pri when Qt is configured
with -developer-build.
Reviewed-by: Michael Goddard
|
|
|
|
|
|
|
|
| |
Using qMemCopy limits QGenericMatrix to plain old types like
float and double. Copying the values normally will allow
copy constructors to work on non plain types.
Reviewed-by: trustme
|
|
|
|
| |
Reviewed-by: trustme
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
src/sql/drivers/ibase/qsql_ibase.cpp
tests/auto/q3sqlcursor/tst_q3sqlcursor.cpp
tests/auto/qsqldatabase/tst_databases.h
tests/auto/qsqldatabase/tst_qsqldatabase.cpp
translations/qt_ru.ts
|
| |
| |
| |
| |
| |
| |
| |
| | |
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>
|