| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
| |
It could happen (with MDI widgets) that the first actions would not be
visible.
Task-number: QTBUG-9560
Reviewed-by: gabi
(cherry picked from commit 864ace14e12cedd8e8f78841249e5309eb0a0795)
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since the introduction of transform properties in QGraphicsItem,
QGraphicsItem::transform() is no longer enough to get the correct
transform of an item.
No auto-test as it involves mouse dragging.
Reviewed-by: Yoann
Task-number: QTBUG-9295
(cherry picked from commit 253b87180e0a6c5db0feaaed7e321139c4ff1643)
|
|
|
|
|
|
|
|
|
| |
We are now checking that the QAction is not related
to the About or Quit button on Mac OS X
Task-number: QTBUG-7540
Reviewed-by: Morten Sorvig
(cherry picked from commit c19cb39ddbfd93802bfe61ecaa4f737a1bd1c1bb)
|
|
|
|
|
|
|
|
|
| |
We should not ignore WM_xBUTTONUP messages after WM_xBUTTONDBLCLK. Treat
these messages like WM_xBUTTONDOWN messages.
Task-number: QTBUG-7172
Reviewed-by: Thierry
(cherry picked from commit 3fbedcd085b3e89e3646bf49264001ee216c5852)
|
|
|
|
|
|
|
|
|
| |
We can't rely on the exposed rect since the item can be outside the view
so we need to regenerate the complete pixmap.
Task-number:QTBUG-8750
Reviewed-by:sroedal
(cherry picked from commit fcb738161efc965e91c3d528c31ac77d3a05ac64)
|
|
|
|
|
|
|
|
|
|
| |
On X11 when creating a widget that has a parent, there is no reason to create a
native window handle right away since we don't know yet if the window is going
to be ever shown.
Task-number: QTBUG-9215
Reviewed-by: Bradley T. Hughes
(cherry picked from commit 1d506981bcc3d2b8aad67989fd7946a0ad826856)
|
|
|
|
|
|
|
|
|
|
| |
This assert was checking that the parent widget for the print dialog
was already created. That's useless since we immediately after call
winId().
Task-number: QTBUG-8684
Reviewed-by: gabi
(cherry picked from commit 6d6df0e2b63f0103ec1f19b4b856b106e295d618)
|
|
|
|
|
|
|
|
|
|
|
|
| |
When QCocoaView receives a keyDown or keyUp event, we translate it to QKeyEvent
and deliver it to qt widgets, propagating if necessary. However if none of Qt
widgets accepted the event we should propagate it back to cocoa - to get a beep
from it, or for example if Qt widget is embedded into a native widget.
Task-number: related to QTBUG-6444
Task-number: QTCREATORBUG-698
Reviewed-by: Richard Moe Gustavsen
(cherry picked from commit 90dfb5e5d8fc8cb841b0762cd88aa4b996c38312)
|
|
|
|
|
|
|
|
|
|
| |
When a key event is delivered to widgets, we should accept the event if the
widget reacted to it in any way - if either the current item has changed or if
the widget scrolled.
Task-number: QTBUG-6444
Reviewed-by: Prasanth
(cherry picked from commit 77230f7ec9e78ec2d57629ea934ceb1d59eb391e)
|
|
|
|
|
|
|
|
| |
This could happen if a section was moved andthen hidden
Task-number: QTBUG-8650
Reviewed-by: Andy Shaw
(cherry picked from commit f9b0efc17962df74a67d81daca5814af93a5fb97)
|
|
|
|
|
|
|
|
|
| |
The problem is that the font changes after the creation of the
buttons and we were setting a fixed size to the datails button.
Task-number: QTBUG-8381
Reviewed-by: gabi
(cherry picked from commit ee379340fcc5ebf8625906f42540c0fb3577f9ac)
|
|
|
|
|
|
| |
Task-number: QTBUG-8270
Reviewed-by: gabi
(cherry picked from commit b912cac358a0a84f72f727767772caad22062a45)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There is the problem that Qt displays half width character
(e.g. alphabet) as full width. This is reported in #QTBUG-1726.
This occurs in the following fonts.
- Monospace font
- Selif font
- IPA font (Ver.0301)
- NSimSun
In Cario and fontconfig, the FT_LOAD_IGNORE_GLOBAL_ADVANCE_WIDTH
is specified as flag of FT_Load_Glyph function to solve this problem.
According to the document of freetype, this flag exists to support
buggy CJK fonts.
So this flag is specified as default flag of QFontEngineFT.
Merge-request: 2319
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@nokia.com>
(cherry picked from commit f18e95849be93b86ff014147086fa538993abc21)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When updating the QTreeViewItem::total field in layout(), we used to
call QTreeViewPrivate::viewIndex() to get the parent item, which is
O(n). We have now introduced 'parentItem' in QTreeViewItem wich makes
this O(1), with a small penality when inserting and removing elements
in QTreeViewPrivate::viewItems.
The QTreeViewPrivate::checkViewItems() is left inside the code for
further debugging.
Reviewed-by: Olivier
Task-number: QTBUG-8885
(cherry picked from commit 7baaea978200c82fdf65e3934cfa373edeca6524)
|
|
|
|
|
|
|
|
|
|
| |
Without clipping, the stroker could consume a huge amount of
memory when scaling up cosmetic, dashed strokes. I also made
QDashStroker clip more aggressively.
Task-number: QTBUG-7832
Reviewed-by: Samuel
(cherry picked from commit ee6c26115959f46621f5a45f3fbe4a49989fd095)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts part of commit e008504b5ec34975e34adf3b1a2b7170d0e4dd38.
The original commit aimed to round up all fractional numbers for the
font to "improve appearance". Rounding up the last advance of a set
of advances in a glyph layout, however, breaks text layout completely,
since the layout of text will be different depending on how many text
lines is used to represent it (since the last glyph in each line will
have a higher advance than the others.) This was e.g. visible in
Qt Creator when turning on whitespace visualization, as all spaces
then created a format change, thus a new text line in the text layout,
and hence an increase of X pixels in the positioning of the text after
the space, where 0.0 < X < 1.0. I see no negative results of removing
the rounding, but if there are any problems, it has to be fixed in the
usage of the advances not in the advances themselves.
Task-number: QTCREATORBUG-381, QTBUG-8791
Reviewed-by: mae
(cherry picked from commit ef9e7168a8ed3e8149204cf6c604a38db35245c0)
|
|
|
|
|
|
|
|
| |
That is required for the Locals & Watchers view in Creator.
Task-number: QTBUG-7115
Reviewed-by: Thierry
(cherry picked from commit 3b58b103bfa2e2b9bb12a042cbba36fb0a1baf9f)
|
|
|
|
|
|
|
|
|
| |
We now terminate the application as long as Qt
says we can. If not, then we cancel the
termination.
Task-number: QTBUG-6296
Reviewed-by: Morten Sorvig(cherry picked from commit 12308db7663679e42c87aa72c564ec3f9f1a457f)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The obvious fix is to use the previsously computed 'section' as paramatter.
(It is even faster)
But one might wonder why logicalIndexAt() does not return the same result
before and after flipSortIndicator(). The reason is that while being
sorted, in _q_layoutChanged, all the hidden section where unhidden and hidden
again. Leaving some pending computation.
Task-number: QTBUG-7833
Reviewed-by: Gabriel
(cherry picked from commit 188c2ef11e92d04dcf334309c85a7f1b14945aaa)
|
|
|
|
| |
(cherry picked from commit 533bf9e4b7bda99c589f14fb308fa75231196703)
|
|
|
|
|
|
|
| |
GL widgets and native controls have paintonscreen set and bypasses
backingstore. They can thus not rely on the windowsurface flushing
but must be repainted via normal means
(cherry picked from commit ac99b3e243b331d26815b80aab97cdaf0ed06b0f)
|
|
|
|
|
|
|
|
|
|
|
| |
It turns out that setParent_sys is wiping out opacity for the
window regardless of what the value is from before. This patch
does the correct thing, namely look at the WA_WState_WindowOpacitySet
flag.
Task-number: QTBUG-5100
Reviewed-by: cduclos
(cherry picked from commit 06638a4c08aaf86d606abc59f642c3c34815e8e6)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
dynamicSortFilter is turned off
We should not sort when inserting items if the dinamicSortFilter flag
is set to false.
Note that some of the test used to rely on the fact that it was sorted.
Those test have been fixed.
The patch has been contributed to us in the task.
Task-number: QTBUG-7716
Reviewed-by: Thierry
(cherry picked from commit 895b9bedc3746723f6c77754df3c428dbc0661d3)
|
|
|
|
|
|
|
|
|
| |
Use the coordinates passed in the LPARAM parameter, the pt passed with
the MSG is not always correct.
Task-number: QTBUG-7637
Reviewed-by: Denis
(cherry picked from commit 234e849cfc85d5618d2f703bb92701042993d2de)
|
|
|
|
|
|
|
|
|
|
|
| |
Window modal dialogs are shown as sheets on Mac, reusing them is showing
some painting artificats. So make sure we create a new window everytime
a sheet is shown. This only applies to Carbon, the Cocoa versions dont
have this problem.
Task-number: QTBUG-8198
Reviewed-by: MortenS
(cherry picked from commit 08ec00c081ce51a924c65df3998657174f9428b6)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We need to update the sorting column in clear_mapping.
But the problem is that updating the source column create a mapping
(because it uses mapToSource). So we need to clear that wrong mapping again
In _q_sourceLayoutChanged there was an uneeded special case.
The case where the source_sort_column might change was never triggered
because of that. So now that the special case has been removed, we need
to do as in clear_mapping.
The test cover the change in clear_mapping and in _q_sourceLayoutChanged
The problem was shown in the Kopete: https://bugs.kde.org/show_bug.cgi?id=199850
Reviewed-by: Thierry
Task-number: QTBUG-7537
(cherry picked from commit 7b96944a02991e404cdab61e24182b90f5849120)
|
|
|
|
|
|
|
|
|
| |
The native border width need to be taken into account in QRenderRule::boxRect()
Task-number: QTBUG-6855
Reviewed-by: Benjamin Poulain
(cherry picked from commit 6e90192b599cee9b903177a0978198326f667613)
(cherry picked from commit 71f7c1d006d0942fb91e795855bd00a35f226385)
|
|
|
|
|
|
| |
Task-number: QTBUG-6395
Reviewed-by: Samuel
(cherry picked from commit 22573ddffc28135fba2dbb9eb2d50a76cae0a09c)
|
|
|
|
|
|
|
|
|
| |
Not creating screen furniture in full screen caused regression
when swapping into idle screen and back on Nokia 5800.
Task-number: QTBUG-10985
Reviewed-by: Jason Barron
(cherry picked from commit 4a4e5e7d54c559d54e9079dacb9c2fd32770f018)
|
|
|
|
| |
Reviewed-by: Trust Me
|
|\
| |
| |
| |
| |
| |
| |
| | |
4.6-integration
* '4.6' of scm.dev.nokia.troll.no:qt/oslo-staging-2:
Fix regression with Qt::AlignRight on monospaced text in QTextLayout
Back port change d85b149a5c7f3532f8e1a593a79298c9ae38a95f
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
For monospaced fonts, using the width (including the bearing) of the
text to align it to the right hand side, will break alignment of
columns of characters. To fix the problem, we go back to the old
procedure, by using the advance of the text as basis of alignment
instead.
Done-by: thorbjorn
Reviewed-by: Eskil
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fixes right alignment of monospaced text, which was a regression in
Qt 4.6.0. Initially it was fixed in Qt 4.7 only, but the regression was
later deemed severe enough to fix in 4.6.x as well.
Task-number: QTBUG-8864
Reviewed-by: thorbjorn
|
|/
|
|
|
| |
Task-number: QTBUG-10986
Reviewed-by: Jason Barron
|
|\
| |
| |
| |
| |
| |
| | |
4.6-integration
* '4.6' of scm.dev.nokia.troll.no:qt/oslo-staging-1:
Don't use QAtomicInt in statics because they are non-POD.
|
| |
| |
| |
| | |
Reviewed-By: Olivier Goffart
|
|/
|
|
|
|
|
|
|
|
|
|
|
| |
In Symbian^3 OS supports animated wallpapers. Unfortunately animation
is drawn to separate surface underneath the application surface. To
avoid fiddling with system surfaces, Qt apps indicate to the
OS that application does not support animated wallpaper and thus,
system draws a "regular" wallpaper for the application.
This feature is supported only in Sym^3.
Task-number: QT-3148
Reviewed-by: Shane Kearns
|
|\
| |
| |
| |
| |
| |
| |
| | |
4.6-integration
* '4.6' of scm.dev.nokia.troll.no:qt/oslo-staging-2:
Fixed an assert in QMenu
Call eglTerminate() when the last QEglContext is destroyed to free mem.
|
| |
| |
| |
| |
| |
| |
| |
| | |
The code was changed and changed the behaviour. This is
basically a kind of revert.
Reviewed-By: gabi
Task-Number: QTBUG-10735
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We never called eglTerminate() to free memory allocated by
eglInitialize() since it was a fixed allocation that would be used
for the lifetime of an application. The new behavior is to call
eglTerminate() when the last EGL context in the app is destroyed.
Task-number: QT-3383
Reviewed-by: Rhys Weatherley
|
|/
|
|
|
|
|
|
|
|
|
|
|
| |
commit 24b811e53b30546279346ab7b16799be119ab8c4 on 4.7 includes bug
fixes which are needed for 4.6 as well.
1. TouchEnd event was missing
2. pressure in touchpoints was set to 0.0 for non pressure sensitive
touch screens, it should be set to 1.0 for consistency with existing
Qt ports (e.g. mac).
Task-number: QTBUG-10885
Reviewed-by: Bradley T. Hughes
|
|\
| |
| |
| |
| |
| |
| |
| |
| | |
4.6-integration
* '4.6' of scm.dev.nokia.troll.no:qt/oslo-staging-2:
Doc: fix typo
QCompleter: fix misuse of QMap that can lead to crashes
qmake: added possibility to specify the type of an install target
|
| | |
|
| |
| |
| |
| |
| |
| | |
Patch providedin the task.
Task-number: QTBUG-8407
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The internal font database was only populated with .ttf and .ccc files.
This patch adds .ltt as file type.
Without complete font type coverage in the fontstore, we may get a
mismatch in the internal association of font table and fontfamily.
Most probably, this will also fix the crash on SSE Satio's. SSE
seems to use .ltt files already on S60 5.0. An improvement needs to be
verified by an owner of such a device, however.
Task-number: QTBUG-8905
Reviewed-by: Aleksandar Sasha Babic
|
|/
|
|
|
|
|
|
|
|
|
|
|
| |
Currently style defines QStyle::SH_ItemView_ActivateItemOnSingleClick,
which leads to itemview item activation only occur on double-click
(or tap). The item selection work native-like on Sym^3.
As a correction, style needs to check the passed styleoption and
check whether or not the state "Selected" is on. In these cases,
the itemactivation can proceed.
Task-number: QTBUG-10697
Reviewed-by: Miikka Heikkinen
|
|
|
|
|
|
|
|
|
|
|
|
| |
Native menus are dismissed by the key press event.
The Qt application then receives the key up event, as it now has keyboard
focus.
The virtual mouse implementation now filters out select key press/release
which don't match the expected mouse button state.
Task-number: QTBUG-9860
Reviewed-by: Alessandro Portale
|
|\
| |
| |
| |
| |
| |
| | |
4.6-integration
* '4.6' of scm.dev.nokia.troll.no:qt/oslo-staging-2:
Fixed QFont to respect the italics constructor flag.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Creating a QFont with the constructor that takes the italic bool flag
didn't work properly, since the property wasn't set to be resolved.
It may be that the property should *always* be resolved, but to
minimize impact, it's only done now if you pass in 'true' for italics.
Reviewed-by: Eskil
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
After replacing some code with a function call to s60UpdateIsOpaque()
we introduced a crash for widgets that set
Qt::WA_TranslucentBackground. The reason for the crash was that the
Qt::WA_WState_Created attribute was being set before calling this
function, but *not* before setWinId() was being called. This meant that
s60UpdateIsOpaque() assumed that the window was created (and the handle
added to the widget map), but this was not actually the case.
The fix here is to move the call to s60UpdateIsOpaque() after the call
to setWinId() such that those assumptions are true.
Reviewed-by: Jani Hautakangas
|