| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Task-number: 250349
Reviewed-by: Trust Me
|
|
|
|
|
|
|
| |
const getter functions.
Task-number: 254722
Reviewed-by: Trust Me
|
|\ |
|
| |
| |
| |
| |
| |
| | |
This reverts commit a5b11b9031f9a2a97b65e9a6134244249845491a.
The proper fix is 1a7da7096bbda17197738061902f4489af234bc0.
|
| |\ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
both visible and invisible widgets.
This is a quick hack to avoid a crash in Qt when setting a focus on a
visible widget that has invisible parent. Proper fix was committed
into master 1a7da7096bbda17197738061902f4489af234bc0, see it's
description for more details.
Task-number: 254563
Reviewed-by: Thierry Bastian
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
QFont has a feature that you can pass a comma-separated list and it will
walk through the list and match the font that it hits first. There's a
nice static function that X11 and Windows uses, but the Mac was using an
older copied version of it. This old version didn't handle quoting which
is what happens in the style sheet. So, using the same code makes
everything work well. As a bonus, Creator looks correct again.
Reviewed-by: Simon Hausmann
|
| | |
| | |
| | |
| | | |
QFont() returns the app font, not an invalid font.
|
| | |
| | |
| | |
| | |
| | |
| | | |
- When changing the aspect ratio, the video wouldn't update.
- The VMR9 can in some cases try to manage the aspect ratio itself
and then fights our system. This is now disabled.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This won't leak on error case, and will work with arbitrary sizes.
Also changed from int to short as instructed by Samuel.
Reviewed-by: Samuel <qt-info@nokia.com>
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
preserve some consistency. Also added a screenshot of the Object
Insepector displaying a form where its widget has no top level layout.
Reviewed-By: TrustMe
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
On Mac, a widget with a NoFocus policy could still get focus
(if only temporarily) as the result of a native focus event.
In particular, a line edit with a completer should
not lose focus (if only for a brief moment) as a result of the
completer popup being shown. This will for example cause an
item delegate to think that the user has navigated away from
the cell and delete the line edit as a result. This will in turn
cause the completer to access a null pointer.
Reviewed-by: Richard Moe Gustavsen
Task-number: 254456 and 254460
|
| | | |
|
|/ /
| |
| |
| | |
Reviewed-by: Trust Me
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
invisible widgets could cause a crash.
Also, when there is a widget hierarchy A->B->C and A and C are marked
as visible but B is hidden, when the user gives focus explicitely to
C, we should remember that and respect it when B becomes visible.
Task-number: 254563
Reviewed-by: Thierry Bastian
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We were only "constraining" headers if they were large, but ignoring the
small and mini ones. This resulted in the small and mini headers looking
bigger than their normal ones which looked strange. Since the headers
have no real small or mini size for a header, we'll make sure to
constrain them all the same.
Task-number: 221115
Reviewed-by: Richard Moe Gustavsen
|
| |
| |
| |
| |
| |
| |
| | |
No more fonts less than 100%. Toned down the green lines separating
table rows, now gray (or we can try a softer green). Made the table
widt 100%. More coming. the constructors still aren't aligned
properly.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
From a merge request #553 by Gordon Schumacher:
During a build internal to Qt, if a header included by qlocale.cpp
itself includes qlocale.h, then QLOCALE_CPP will never be set. If you
attempt to build qmake from its own .pro file, qmake_pch.h includes
qtextstream.h, which (now) includes qlocale.h, thus causing a compile
error trying to call the QSystemLocale(bool) function
Inspired-by: Gordon Schumacher <gordon@rebit.com>
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Thiago Marcos P. Santos (1):
Fixed sub-attaq example build
Request-url: http://qt.gitorious.org/qt/qt/merge_requests/564
Reviewed-by: Denis Dzyubenko <denis.dzyubenko@nokia.com>
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Some older systems support monotonic timers, but not POSIX.1-2001. The
sysconf() function is documented to return -1 if a feature is not
supported, otherwise it returns a value that's dependent on it's
argument. For POSIX.1-2001 compliant system, the value is 200112L, but
on other systems it may just return 1, for example.
Because of this, we check for the -1 return value (feature missing),
instead of relying on a specific (positive) return value.
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
jieshuzheng (1):
Remove the redundant timer kill and start when the two
Request-url: http://qt.gitorious.org/qt/qt/merge_requests/573
Reviewed-by: Eskil Abrahamsen Blomfeldt <eblomfel@trolltech.com>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
QTimer::start(int) is made in succession
If you restart the QTimer like the following code snippet shows, the
timer will get killed and started twice.
QTimer timer;
timer.start(100);
timer.start(1000);
Since QTimer::start(int msec) calls QTimer::setInterval(int msec), and
QTimer::setInterval(int msec) will kill the timer and start another one
if there is already a timer running. And QTimer::start() will do the
same thing again. It is a performance penalty here. Under Windows, it
will result in one extra call of SetTimer(). And under Symbian, it will
result in one extra new and delete of CPeriodic and adding and removing
it from AS.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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
|
|\ \ \ \
| | |_|/
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
src/opengl/gl2paintengineex/qpaintengineex_opengl2.cpp
tests/auto/qgraphicswidget/tst_qgraphicswidget.cpp
tests/auto/selftests/expected_skip.txt
tests/auto/selftests/tst_selftests.cpp
|
| | | |
| | | |
| | | |
| | | |
| | | | |
KDE Bug: https://bugs.kde.org/show_bug.cgi?id=191759
Reviewed-by: Bradley T. Hughes
|
| | | |
| | | |
| | | |
| | | | |
Better late than never.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The batch-blits buys us nothing and this is much more readable.
Reviewed-by: TrustMe
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Cherry-pick of 548da9a5434d615456a7a6efda3380b7138c6000 and some
earlier changes predating public repo.
Note that this test is not failing if using Qt 4.5 only.
However, it fails if using Qt 4.5 selftests against Qt master testlib.
We want to be able to use master testlib to run 4.5 testcases,
and this change does no harm when using Qt 4.5 testlib, so backport
it to 4.5 for convenience.
Original change description follows:
A few tests use printf, which means they interfere with the XML test
logging. Blacklist them for the XML test.
Note that these tests happened to pass under the old test logger
implementation. That was because the test logger always printed XML
tags on a single line, and the printf calls contained no special XML
characters. The test logs generated were technically valid XML but
contained extraneous text.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
DirectFB and Qt treats these things rather differently so the mapping
just doesn't work very well. Only use DirectFB for SourceOver stuff
(which is the default mode anyway)
Reviewed-by: Donald <qt-info@nokia.com>
|
| | | |
| | | |
| | | |
| | | | |
Reviewed-by: David Boddie
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The new glyph cache may return null images for e.g. space characters.
Task-number: 253468
Reviewed-by: Samuel
BT: yes
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Only the Solution Generator was using the fixFilename() function, so
under some circumstances the solution filename wouldn't find the
correct vcproj file to include. This created a problem with
network-chat.vcproj.
Task-number: 254772
Reviewed-by: joao
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Task-number: 254451
Reviewed-by: trustme
BT: yes
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Task-number: 254451
Reviewed-by: eskil
BT: yes
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
in atomic operations, we declare Interlock... functions in the namespace
That can confuse the compiler because they are also declared in another
header outside the namespace.
Same problem in clucene where we include windows.h from within the NS.
Task-number: 254214
Reviewed-by: ogoffart
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Task-number: 254549
Reviewed-by: TrustMe
|
| | | |
| | | |
| | | |
| | | | |
Reviewed-by: TrustMe
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Previously we allowed RGB32 but forced fallbacks for all drawing
operations. It turns out blitting operations doesn't work right either
so we'll rather just disallow this format altogether. See also
36ae58e7a6a888d3ae7bd162d59daada550bbfb1
Reviewed-by: Donald <qt-info@nokia.com>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Due to incompatibilities between RGB32 in DirectFB and Qt we can't use
RGB32.
Reviewed-by: Donald <qt-info@nokia.com>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
We were adding two times in the QActionPrivate list the entry for
the current QGraphicsWidget if the action was existing before.
Task-number:KDE
Reviewed-by:bnilsen
BT:yes
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
An optimization was made to the sorting of QFileDialog to sort only
the current root (meaning what the user see). This avoided slowness
when the model was big with lots of leafs. The problem here is
for the treeview, the root is always the same, we expands only
nodes. In that case, a recursive sorting is needed to ensure that
all expanded nodes are correctly sorted (and filtered). This will
be slower that's why i use an hidden flag in the d pointer to
deactivate the recursive sort for the QFileDialog.
Task-number:254701
Reviewed-by:olivier
BT:yes
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
main function has a return value now.
On the HTC this example didn't work, because this stupid thing sends
two resize events, if the SIP is opened (and only one if it is closed).
Reviewed-by: mauricek
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When QWidget::scroll() is called on a widget with WA_PaintOnScreen,
scroll the dirty region.
Task-number: 254742
Reviewed-by: bnilsen
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
If pixmaps were added through QIcon::addFile() with different sizes
than the sizes of the pixmaps themselves, streaming the icon in didn't
work properly.
Task-number: 254374
Reviewed-by: Kim
|
| | | |
| | | |
| | | |
| | | | |
Reviewed-by: Kim
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The bounding rect computed in fixup() is one pixel too wide, causing
potential memory corruption by painting outside device boundaries.
Reviewed-by: Trond
|