| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
We now commit the text if the mouse handler is invoked. This prevents
the case where the VK cannot be brought up because the widget is the
only focusable widget and is stuck in inline edit mode.
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Earlier used CSendUi required extensiva capabilities to work correctly,
that's why "new email" option in desktop services example application
did not work correctly with self signed capabilities.
RSendAs requires lower capabilities since SendAs server (separate
process) takes care of necessary actions to send the message.
|
|/
|
|
| |
its width on horizontal scrollbar (and height on vertical scrollbar).
|
|
|
|
| |
Got lost with dc177883bf98a68e61c9a9cda7e1ba9464079275
|
| |
|
| |
|
|
|
|
|
| |
There were no objections from the field with ing one Year of
Tech Previews.
|
|\ |
|
| |\
| | |
| | |
| | |
| | | |
Conflicts:
tests/auto/qlocalsocket/tst_qlocalsocket.cpp
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We didn't actually check the depth of the target window before
calling the qt_x11_drawImage() fu, that will only work with
depths >= 24.
Task-number: 255311
Reviewed-by: Samuel
BT: yes
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
events."
This reverts commit 7314c07a3e443b1d5349b419a03db8d41ca43f7e.
As reported by Eike, this patch caused several problems for Qt Creator.
Potentially it may cause problems for other (external) applications as well.
An alternative fix (scheduled for 4.5.x) needs to be found for tasks
254456 and 254460.
Reviewed-by: Richard Moe Gustavsen
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The reason is that cocoa looses the first responder when
we raise the fake window inside the MDA area. So we need
to re-set the first responder again
Task-number: 255040
Reviewed-by: Trenton Schulz
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
There were several problems with antialiased text in 16 bit mode
under Windows. No gamma correction was done, yet we prepared the
cached glyphs for gamma correction. The mask format we rendered
the glyphs into was also set to the desktop depth, which implied
that information was lost and the text looked rather odd.
Reviewed-by: Samuel
BT: yes
|
| | |
| | |
| | |
| | |
| | |
| | | |
We were saying that it connected to accepted it all these cases, but it
actually is doing some nice magic that makes sense assuming you document
it.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
No progress bars on the mac show text and it would be bad if we allowed
it. There's nothing stopping people from connecting the valueChanged()
signal to a slot and have a real label layed out correctly that actually
updates with the amount of time it takes to complete, etc. This is more
what they do on Mac OS X if they decide to show a label.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
QMotifStyle
Same fix as in e9a7e43031d7c1ee712e43be682c4e2c183759c4 but with motif
Reported by https://bugs.kde.org/show_bug.cgi?id=193911
Task-number: 255138
Reviewed-by: jbache
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This was quite a bug and it showed to some issues that I hadn't taken
into account when doing the initial port to Cocoa. The issue was that we
weren't "merging" items into the application menu if an item had already
been associated with it. Which seems OK for applications that create one
window with one menubar, but breaks down horrible when you have multiple
windows with each having their own menubar. The result is that items in
the application menu potentially go to the wrong window (and the
potential crash). Since there can only ever be one "Quit", "About", or
"Preferences" menu item in Cocoa, we need to make sure that we keep
these items in sync whenever we switch the menubar or remove actions
that are being deleted. That's what we do here.
FWIW, QActions with "ApplicationSpecificRole" for their menu role have
potential to cause memory leaks or other bugs if abused. If you are a
happy open source hacker who wants a thankless job, solving them would
get you lots of goodwill in my book.
Task-number: 255038
Reviewed-by: Richard Moe Gustavsen
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The blend functions assume the width / height of the images being
blended to be greater than 0. A width of 0 caused the first iteration of
a duff's device memcpy (QT_MEMCPY_USHORT) to be executed, thus blending
8 pixels instead of none.
BT: yes
Task-number: 255014
Reviewed-by: Trond
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The R and B channels were swapped on little endian machines with
BGR layout.
Task-number: 254934
Reviewed-by: Samuel
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
| | |
| | |
| | |
| | |
| | | |
KDE Bug: https://bugs.kde.org/show_bug.cgi?id=191759
Reviewed-by: Bradley T. Hughes
|
|/ /
| |
| |
| |
| |
| |
| | |
Called setFocus only when the widget does not already have the focus.
This should remove unncessary calls to FocusChanged since CCoeControl
always calls FocusChanged when SetFocus is called, even there was no
changes in focus.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
RevBy: Sami Merila
|
| |
| |
| |
| |
| | |
If any of those hints are present, complex input is not possible,
so input methods should be turned off on Windows.
|
|\ \ |
|
| | |
| | |
| | |
| | | |
tab content.
|
| | |
| | |
| | |
| | |
| | | |
Otherwise the update would always end up with the selection being in
the first block.
|
|/ /
| |
| |
| |
| |
| | |
S60Style did not implement SE_ItemViewItemCheckIndicator if given
option was somethign else than QStyleOptionViewItemV4. This causes some
autotests to fail. Added appropriate query for QCommonStyle.
|
| |
| |
| |
| | |
Semi-colons, colons, they all look the same to me.
|
| |
| |
| |
| | |
On S60 one should get virtual keyboard.
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | | |
If any of those hints are present, complex input is not possible,
so input methods should be turned off on X11.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Order is 'soft to hard' W:, X: ... A:, Z: Duplicated font file
names are ignored. That should imitate the font loading behaviour
in the fbSrv.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
When events are comming, exactly that widget will be aske for InputContext.
|
| |\ \ |
|
| | | |
| | | |
| | | |
| | | | |
The simulated style will by default try to load the 'Default.blob'
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Previously, the input context would not get updated on every
selection update.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
RevBy: Trust me
The fix is almost identical to the one made for QLineEdit.
|
| | | | |
|