| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
| |
By default if the gesture is ignored, only gestures in the started state
are propagated, and accepting a gesture in the started state adds an
implicit grab meaning all the following events in the gesture sequence
will be delivered to that widget. This is similar to the way QTouchEvent
is propagated.
Also added a hint, which specifies if gestures in any state can be
propagated to the widget which has enabled the hint.
Reviewed-by: Thomas Zander
|
|
|
|
| |
Reviewed-by: trustme
|
|
|
|
| |
Reviewed-by: trustme
|
|
|
|
| |
Reviewed-by: trustme
|
|
|
|
| |
Reviewed-by: trustme
|
|
|
|
|
|
|
| |
Oops, apparently we forgot to add a function for unsubscribing a
graphics object from a gesture. Fixing it now.
Reviewed-by: trustme
|
|
|
|
| |
Reviewed-by: David Boddie
|
|
|
|
|
|
|
|
|
| |
For some reason, Cocoa tells us twize whenever a selection
change occurs in the native file dialog. This patch inserts
a check that the selection actually changed before emitting
any signals
Rev-By: Prasanth
|
|
|
|
|
|
|
|
|
| |
standardWindowButton:NSWindowDocumentIconButton will not return a valid
NSButton unless you call setRepresentedURL or setRepresentedFilename
for the NSWindow. This patch makes sure that setWindowIcon_sys() sets
the icon using a valid NSButton.
Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@nokia.com>
|
|\ |
|
| |
| |
| |
| | |
Reviewed-By: Denis
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Change 9551b8c349ce4e15a57c24a2408ee1b73c2b7510 enabled documentMode on the
tabbar in Assistant. To make it look more native we also remove the margin
around the tabwidget.
Reviewed-by: Prasanth
|
| |
| |
| |
| |
| |
| | |
DataLocation now behaves as on the other platforms,
QCoreApplication::organizationName() and applicationName()
is included in the returned path.
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
| |
Task: QTBUG-4988
68c0e6a8ba1e92bf0152adcaa86eebb83dcfd1d8 introduced
a regression preventing the mac-spesific standardIcon
code form being called.
Call the Mac code if desktopSettingsAware is set.
(QIcon::themeName() is only set on X11)
|
|
|
|
|
|
| |
According to people responsible for the test, it is not
necessary. This partially reverts commit
b1f9882fa52745c922eb0109daa011908214dcf7.
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
This also adds QStyleOptionTabWidgetFrameV2 so that we do not have
to do ugly hacks in the style to obtain it.
Task-number: QTBUG-5187
Reviewed-by: ogoffart
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
While drawing the tabbar frame, mac style needs the QTabBar pointer to
calculate the correct size.
Since the QTabWidget also uses the PE_FrameTabBarBase to draw background
of the corner widgets, the mac style has to use position passed with the
style option. This only works with horizontal tabs.
Reviewed-by: Jens Bache-Wiig
|
| |
| |
| |
| |
| |
| | |
This was a platform regression for the cocoa platform
Reviewed-by: Prasanth
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The subcontrol rect offset was correctly reporting
not to work on Vista style. The problem was that we were
getting the size of the arrow by subtracting the xoffset.
But this would mean that the
Reviewed-by: ogoffart
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When a tool button is not in a tool bar on XP and Vista it will get a
slightly different appearance from normal tool buttons. I resolved
this by drawing a normal tool button with a divider line on top
if the autoraise property is not set on the button. (which is by
default enabled only for buttons in a tool bar).
Task-number: QTBUG-5061
Reviewed-by: prasanth
|
| |
| |
| |
| |
| |
| |
| |
| | |
Dragging is handled by a seperate window in document mode. The currently
selected tabbar item is drawn to a pixmap for this purpose. That
paintdevice was not initialized correctly. (e.g. font)
Reviewed-by: Trond
|
| |
| |
| |
| |
| |
| | |
There is no reason to use QMap when the key is a pointer.
Reviewed-by: Thomas Zander
|
| |
| |
| |
| | |
Reviewed-by: David Boddie
|
| |
| |
| |
| |
| |
| |
| | |
When application closes and we haven't deleted the unregistered gestures
and gesture recognizer, we should delete them.
Reviewed-by: Thomas Zander
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When there are several gesture recognizers registered for the same
gesture type, we need to know which recognizer we need to get a state
object for since those QGesture objects are tied to the recognizer that
created them.
Reviewed-by: Thomas Zander
|
| |
| |
| |
| | |
Reviewed-by: trustme
|
| |
| |
| |
| | |
Reviewed-by: Thomas Zander
|
| |
| |
| |
| | |
Reviewed-by: Denis Dzyubenko
|
| |
| |
| |
| |
| | |
Our tests now call the recently converted registerRecognizer using a proper
static method.
|
| |
| |
| |
| |
| | |
The widget() getter is still publicly documented, follow the lead of
other events to make the setter internal.
|
| |
| |
| |
| |
| | |
As QApplication is a singleton this makes usage of these
easier and also in line with many other methods on the class.
|
| |
| |
| |
| | |
Reviewed-By: TrustMe
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
While querying for the text in the pasteboard, it was looking in the
wrong place. The helper function qt_mac_get_pasteboardString() always
searched in generalPasteboard instead of the pasteboard referred by the
QMacPasteboard.
Reviewed-by: MortenS
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
On accepting one gesture Qt can automatically cancel other gestures
that belong to other targets. The policy is normally set to not cancel
any other gestures and can be set to cancel all active gestures in the
context. For example for all child widgets.
Reviewed-By: Denis Dzyubenko
|
| |
| |
| |
| | |
are done
|
| |\
| | |
| | |
| | | |
4.6-WM_NULL-driven
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Emit the QDesktopWidget::workAreaResized() signal when the _NET_WORKAREA
property of the root window changes.
Merge-request: 1111
Reviewed-by: Denis Dzyubenko <denis.dzyubenko@nokia.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Qt up to 4.5.x is missing whole setup of multimedia keys already defined by X
Merge-request: 1742
Reviewed-by: Denis Dzyubenko <denis.dzyubenko@nokia.com>
|
| | |
| | |
| | |
| | |
| | |
| | | |
Decided after review by David Boddie.
Reviewed-by: trustme
|
| | |
| | |
| | |
| | | |
Reviewed-By: trustme
|
| | |
| | |
| | |
| | | |
Reviewed-by: trustme
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The default height of tab bar is 22 pixels in Snow Leopard. We used to
draw tabs taller than 21 pixels to a pixmap and stretch to the required
size. The limit is now changed to 22 pixels (which is the most common
use case). The stretched drawing is not perfect in Snow Leopard due to
some changes in how HITheme draws tabs.
Reviewed-by: Jens Bache-Wiig
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When a tab is clicked and mouse is moved outside that tab, it should
be drawn as normal (not in sunken state).
Reviewed-by: MortenS
|
| | |
| | |
| | |
| | | |
Reviewed-by: trustme
|
| | |
| | |
| | |
| | | |
Reviewed-by: Denis Dzyubenko
|
| | |
| | |
| | |
| | | |
Reviewed-by: Denis Dzyubenko
|
| | |
| | |
| | |
| | | |
Reviewed-by: Denis Dzyubenko
|