| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Reviewed-by: thiago
|
|
|
|
|
|
|
|
|
|
|
| |
In the updated examples, the drag operation is changed in the drop-event
handler, which was not handled correctly in the Cocoa. This is now
supported for drag and drop from same application. If the drop was to
another application, the drag will return the result from the last
drag-move event.
Task-number: 252103
Reviewed-by: nrc
|
|
|
|
|
|
|
|
|
| |
The QIcon::pixmap() call would always load and validate any svg file
that was used for a QIcon, even though there was a cached pixmap
for that particular size.
Task-number: 248848
Reviewed-by: Kim
|
|
|
|
|
|
|
|
|
| |
If we have a rect-clip where we actually had spans (used for
cleartype) and then reused that clipdata, we would never re-create the
spans, which would mean that future drawing would be filtered based on
the old clip
Reviewed-by: Samuel
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since we have to update the brush for each paint command anyway keeping
the state of the brush and caching the value of simpleBrush makes no
sense.
Also, most times when filling with a brush
QPaintEngineEx::fillRect(const QRect &, const QBrush &) is called in
which we never got a brushChanged() anyway.
Reviewed-by: Donald <qt-info@nokia.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since we have to update the brush for each paint command anyway keeping
the state of the brush and caching the value of simpleBrush makes no
sense.
Also, most times when filling with a brush
QPaintEngineEx::fillRect(const QRect &, const QBrush &) is called in
which we never got a brushChanged() anyway.
Reviewed-by: Donald <qt-info@nokia.com>
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Should have been part of 8aa8997f18afb85cb17f5b2a875a004302df4c72
Sorry the HOWTO file was not entirely clear that the *.qch needs
to be updated too.
Task-number: 251421
Reviewed-by: kh
(cherry picked from commit 0b3ef41cdc8fef79d184e91d2542cc34f7dec5e1)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
into it."
This reverts commit 0985805ab3c7de5b15c115a98afb15944b6d93b9.
The Elastic Nodes example shows a black background for the cache pixmap
if the call to fill isn't there. Alexis and I both agree that it makes
no sense that we fill the pixmap with transparent pixels instead of
just drawing with QPainter::CompositionMode_Source, but since this
regression was introduced after 4.5.0 was released we must revert before
we investigate further.
Reviewed-by: Alexis
(cherry picked from commit 183cb6052c45d7c83e36c78da4e2c59c768209c7)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This fixes a bug in 4.5.0 where cached items that call update() after
they have been moved or transformed failed to get a call to paint(),
so the last cache image was used to draw. The easiest way to reproduce
this bug is in the Elastic Nodes example. If you press, wait, then
release, the nodes will consistently move to sunken state, then back
to normal state. But if you click quickly while moving the mouse, the
nodes will stay sunken.
The bug was that the item was marked as dirty as a result of being moved,
and when the mouse button was released, the node item's call to update()
was discarded, as the item was "already dirty".
The fix is to allow invalidation of the cache even if the item is
marked as dirty.
Reviewed-by: bnilsen
(cherry picked from commit 08feb22f9a924ce120da8b5c6e1669d2a630dd54)
|
| |
| |
| |
| |
| |
| |
| | |
The #ifdef was typed wrong.
Reviewed-by: Prasanth Ullattil
(cherry picked from commit 924feac07729b680fbd337e3773c747b64e1da61)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Previously we were calling two times itemChange on the parent to give
QGraphicsItem::ItemChildAddedChange. We don't need that. One is enough.
BT : yes
Task-number: BT
Reviewed-by: Andreas
(cherry picked from commit 95b7c50e503dd4743e22c35f341aa31105ea7d73)
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Ensure that we don't divide by 0 when two nodes are exactly on top
of each other.
Reviewed-by: Alexis
Reviewed-by: Joao
(cherry picked from commit 6a3735a47de8a9851e7795cf023d95d81867260d)
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
should have been part of c8285ec610b02f440f692be90aed1e6925a8675
Task-number: 251346
Reviewed-by: TrustMe
BT: yes
(cherry picked from commit 92f07dcd690d596e2d6cc32211c142cd0e25fd97)
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Remove the *_tr_TR.ts files added in change
5e3cae2754bf5f50aa10fef2c8d3bb7d33407b96 and remove their entries from
.pro files to prevent them coming back next time someone does "make ts".
Reviewed-by: Trust Me
(cherry picked from commit b2112b17e427274ac0610416b2941b091314f5ad)
|
| |
| |
| |
| |
| |
| |
| | |
Add Copyright message as requested by Legal, and update .ts files again.
Reviewed-by: Trust Me
(cherry picked from commit 3bcbfcfa466890469f3053a3c5987bc2cf85317b)
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
If we don't have a sheet, we need to recreate it in Cocoa.
Unfortunately, we neglected to reassign the NSWindow pointer in that
case, so the program would crash.
Reviewed-by: Richard Moe Gustavsen
(cherry picked from commit 9d9889682c79bacb803ef5613502e7307c1d16bd)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Update the text of the About Qt dialog, as directed by Legal. Note that
this change breaks string freeze as the text is translatable, however
Legal has decided that shipping legally correct text has priority over
shipping complete translations. This change includes updated .ts files
to correct the source strings, but no updated translations.
This change also removes out-of-date licensing text from the About
dialogs of Designer, Assistant, Linguist, QtConfig and qdbusviewer.
Those particular changes should not break translations as they only
remove translatable strings and do not modify any others.
Task-number: 247608
Reviewed-by: Trust Me
.....review will be conducted after submission.
(cherry picked from commit 5e3cae2754bf5f50aa10fef2c8d3bb7d33407b96)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In the docs, index.html had a statement about licensing that is no
longer true, plus the file it linked to longer exists. This change
removes the offending paragraph from the docs.
Task-number: 251348
Reviewed-by: Carlos Duclos
(cherry picked from commit 81c7a8b453726bb4aff11f2382284fc144eeda78)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Cocoa's font manager uses "first responder" which is a great idea, but
breaks as soon as we change windows. Thankfully we can just set the
target and we are OK. An upshot is that we don't need the delegate, but
I'm not going to push my luck on that.
Reviewed-by: Richard Moe Gustavsen
(cherry picked from commit 7c815bc2d4ea922d75f49f7dc29c81362ce5210e)
|
| |
| |
| |
| |
| |
| |
| |
| | |
I have now inspected all 4.x.y version numbers appearing in the depot.
All remaining instances appear to be acceptable.
Reviewed-by: Trust Me
(cherry picked from commit a46f54e0ad78ccb4ffaeee6befc7429f93740375)
|
| |
| |
| |
| |
| |
| | |
Reviewed-by: TrustMe
BT: Yes
(cherry picked from commit e85867003ca1741f378b1f58f4dd9d48577a5d9b)
|
| |
| |
| |
| |
| |
| |
| |
| | |
Replace with %VERSION%, so we don't need to fix this for every release.
Task-number: 251417
Reviewed-by: Trust Me
(cherry picked from commit 2df5b45eed7059862e9dd10a74c19310266b9d55)
|
| |
| |
| |
| |
| |
| |
| |
| | |
Use %VERSION% so that we don't have to fix this for every release.
Task-number: 251418
Reviewed-by: Trust Me
(cherry picked from commit cfa04d53ff58d45d7811637c8be76099740d25c5)
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Doc still referred to 4.4.0-rc1 - replace with %VERSION% so we don't
have to keep updating this.
Task-number: 251419
Reviewed-by: Trust Me
(cherry picked from commit 569394738995b6792f6e4866f0daf12897975ad4)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This page is not linked from anywhere, and its content is horribly
out-of-date.
Task-number: 251420
Reviewed-by: nrc
(cherry picked from commit c138c9e80acabcf1d9a712a7ebd2b2a7d6135d8b)
Conflicts:
doc/src/qtcocoa-known-issues.qdoc
|
| |
| |
| |
| |
| |
| | |
Task: 251421
Reviewed-by: Trust Me
(cherry picked from commit 8aa8997f18afb85cb17f5b2a875a004302df4c72)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The unicode characters between 0xF700 & 0xF8FF are special function-key
code characters used by the NSEvent. These characters have to be ignored
when converting to a QString.
Task-number:244486
Reviewed-by:nrc
(cherry picked from commit 5d39d424a92d89243207d8370d0fa1c6c8061668)
|
| |
| |
| |
| |
| |
| | |
Reviewed-by: TrustMe
BT: Yes
(cherry picked from commit 2da87118ac000f754ca09ad2b14f1ec80a59b985)
|
| |
| |
| |
| | |
(cherry picked from commit c01ce578761aefc2c1780047aa666eb7ee96159f)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Don't state a specific version number, or we'll keep forgetting to
update it.
Task-number: 251338
Reviewed-by: Trust Me
(cherry picked from commit 08934a1647d60150d260275b4aac7d680bce3cfe)
Conflicts:
FAQ.txt
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The previous logic caused a license check when the eval
license file was missing.
Reviewed-by: Jason McDonald
Task-number: 251339
(cherry picked from commit 8eb08c8c294f00763961e86cc3370b0ef78c8976)
|
| |
| |
| |
| |
| |
| |
| |
| | |
Restore the text that is omitted for a minor release but included in
patch releases. Also fixes obsolete link to changes files.
Reviewed-by: Trust Me
(cherry picked from commit e389dc42a1d3d473eac34987767b94dbe623a275)
|
| |
| |
| |
| | |
(cherry picked from commit 095c4209fe8fea6d46cc6c1486d2bc6471e8f0a5)
|
| |
| |
| |
| | |
This reverts commit b173f1671fd35c6ae674f5368f7a8b66a0f15322.
|
| | |
|
| |\ |
|
| | |
| | |
| | |
| | | |
(cherry picked from commit 90d7509e4a1543e43a49bfb25dd672d824c4fde3)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The comment in the code pretty much says it all, so I'll repeat it:
This is a workaround for NSToolbar. When a widget is hidden by
clicking the toolbar button, Cocoa reparents the widgets to another
window (but Qt doesn't know about it). When we start showing them,
it reparents back, but at this point it's window is nil, but the
window it's being brought into (the Qt one) is for sure created.
This stops the hierarchy moving under our feet.
Task-number: 251294
Reviewed-by: Prasanth Ullattil
(cherry picked from commit 139265031939d676f049edd2c91918040e0659b4)
|
| | |
| | |
| | |
| | |
| | |
| | | |
Reviewed-by: TrustMe
BT: Yes
(cherry picked from commit 0aa3203fa13bfbc42e77488765023832934dd36b)
|
| | |
| | |
| | |
| | | |
(cherry picked from commit 602da82d3c9413df41eb5b17bdf7e3c1586316b5)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Task-number: 251346
Reviewed-by: TrustMe
BT: Yes
(cherry picked from commit fc8285ec610b02f440f692be90aed1e6925a8675)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
have a version number, so we do not have to update it each release.
Task-number: 251352
Reviewed-by: TrustMe
(cherry picked from commit 90ff6b0ad7397a6892185e8340d58dab4b85b032)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
marked getInt() as since Qt 4.5 and finally modified the StandardDialogs
example to reflect the fact that getInteger() is deprecated.
Task-number: 251288
Reviewed-by: nrc <qt-info@nokia.com>
BT: Yes
(cherry picked from commit 08dff2935af2d71f2fe76182079da636c1bb6f5b)
|
| | |
| | |
| | |
| | | |
(cherry picked from commit 78659fbe2d4ad8a01b41cb485f57b4a66c031fd5)
|
| | |
| | |
| | |
| | |
| | | |
Changelog
(cherry picked from commit b6a50971f51618a3965605d9223c8b2b06c23f29)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This has to do with coalesced updates. The easy fix for now is
to fix QtDemo itself, meaning: always use a steady timer for
redrawing the viewport of the graphics view (as opposed to let
each item on screen calling update whenever they move)
Task-number: 250667
Reviewed-by: Trenton Schulz
(cherry picked from commit 4aa94a353224c14265446276277a91339f2e415d)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Amend fd5f83e612729cebc5395c992bd98628bb9ea25f
calling fetchMore in create_mapping was a bad idea bacause it may lead
to infinite recurtion
Make a special case for hasChildren instead
Task-number: 250023
Reviewed-by: Marius Bugge Monsen
BT: yes
(cherry picked from commit f8fba0d48a1f30540ddf15f0d36f415b192d1d8b)
|
| | |
| | |
| | |
| | | |
(cherry picked from commit 97ff2bde044838be0d5210a86c2fafd23c05d994)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The data passed to XChangeProperty should be long arrays, as this is
what Xlib expects.
Task-number: 244062
Reviewed-by: Rhys Weatherley
(cherry picked from commit 1ae4c7b989b04f89a5069d5a5db78c0d8914972b)
|