| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Also changed qdoc not to warn about undocumented parameters
if the function is marked with the \reimp command.
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
There was a bug in the Carbon code when an item went in full-screen,
than out with a unified toolbar. In those cases the toolbars would end
up getting but into the mainwindow area. The reason this was happening
was that we were calling transferChildren() after we had set up our
toolbar. This cause problems because we end up pulling the QToolbars
right out of the unified toolbar. The easiest way to solve this is to
just update the status on it again. This should solve any issues. I also
added some logic to avoid calling this too many times in that one case.
Luckily, this seems to only affect Carbon.
Task-number: 254462
Reviewed-by: Jens Bache-Wiig
|
| |
| |
| |
| |
| | |
Task-number: 256818
Reviewed-by: Trenton Schulz
|
|\ \
| |/ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
The windowDidResize notification now differentiates an internally
triggered resize from a user triggered resize.
Task-number: 256269
Reviewed-by: Norwegian Rock Cat
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Frameless windows wouldn't get shadows in Cocoa, which they do in
Carbon. You can argue over who is more correct, but the fact is they
can't be inconsistent. Since Cocoa is the newcomer, I'm bending that.
Though it would seem useful to have an ability to provide some developer
control over the shadow. At the moment, the only thing we have to ensure
is that we always turn on the shadow.
Task-number: 254725
Reviewed-by: Denis
|
| |
| |
| |
| |
| |
| | |
Also fixed a few qdoc error reports.
Task-number: 162182, 222650
|
| |
| |
| |
| |
| |
| |
| | |
It was only taking the sizeHint into account
Task-number: 141355
Reviewed-by: jasplin
|
| |
| |
| |
| | |
On some systems, math.h still doesn't define M_PI.
|
| |
| |
| |
| |
| |
| |
| | |
Commercial license headers belong in source packages only. The repo
must have the pre-release license headers.
Reviewed-by: Trust Me
|
| |
| |
| |
| | |
Reviewed-by: Trust Me
|
|\ \
| |/ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is mainly a stop-gap solution for 4.5.x. It trades painting performance
for correct painting.
Commit 7988d05da changed the opaque test from q->testAttribute(Qt::WA_OpaquePaintEvent)
to qt_widget_private(w)->isOpaque in qt_mac_update_widget_posisiton. This means
we'll do optimized moves in more cases. Unfortunately it also causes painting errors
in some cases (see the task).
Revert the commit for now to put the 4.5 branch in a god shape.
Task-number: 252295
Reviewed-by: nrc
|
| |
| |
| |
| |
| | |
Fixes error:
src/gui/kernel/qevent_p.h:62: error: invalid use of incomplete type ‘struct QKeyEvent’
|
| |
| |
| |
| |
| |
| |
| | |
Replace the SIZE constant with an Enum with a Qt-ish CamelCased name
(since SIZE conflicts with the system headers).
Reviewed-by: TrustMe
|
| |
| |
| |
| | |
We don't want to pull in too much if we can avoid it.
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This significantly improves the support for
higher DPI-values on these platforms by
ensuring that common pixelmetrics are
scaled accordingly. In addition we mark all
Qt apps as DPI-aware on Windows 7 by calling
SetProcessDPIAware. We also changed the
way we draw pixmaps on the mac paintengine
when using dpi scaling > 1 to ensure smooth
pixmap scaling.
Reviewed-by: nrc
Task-id: 242417
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
10.6 does a lot of image synthesis for us when we put up a tiff, which
is great because we don't have to do a thing and it will work with all
the applications out there. This means we don't need our PICT convertor
on 10.6 for 32-bit apps. However, this magic doesn't exist in earlier
versions of Mac OS X, so we have to keep it around (along with the
QuickTime symbol resolving) there.
Reviewed-by: Morten Sørvig
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
WM_NCHITTEST has to return the location type based on the position,
instead of returning just true or false.
Reviewed-by: Marius Storm-Olsen
|
|\ \ \
| |/ /
| | |
| | |
| | | |
Conflicts:
src/gui/kernel/qapplication_x11.cpp
|
| | |
| | |
| | |
| | |
| | |
| | | |
Removed lots of places where we check for Tiger. Now we can assume it.
Reviewed-by: Morten Sørvig
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
These are used enough (at least on the mac) to justify them being
accessible in a private header. As a bonus it "hides" the actual
container being used, so we could potentially sway it out with something
different.
Reviewed by: Jens Bache-Wiig
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Ah! One less ###!
The scroll functions in Carbon and Cocoa don't scroll the regions that
have been marked dirty. In the past, we killed performance by updating
the whole view. We got a workaround for Carbon in the form of an SPI,
but I wasn't aware of a corresponding item in the NSView API, but it is
there publically and available in 10.5. Fast scrolling in Cocoa now for
people who like to use the keyboard.
Reviewed by: Morten Sørvig
|
| |\ \
| | |/
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
src/3rdparty/webkit/VERSION
src/3rdparty/webkit/WebCore/ChangeLog
src/3rdparty/webkit/WebKit/qt/ChangeLog
tests/auto/qgraphicsitem/tst_qgraphicsitem.cpp
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
After discussing with some of the Objective-C
people I have finally got a fair number of the
warnings to disappear in both 10.5 and 10.6. I
also took the opportunity to remove a bunch of
other warnings.
Reviewed by: Morten Sørvig
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
gcc 4.1.2 on X11 somehow confuses assignment of a temporarily
constructed QSettings object to a reference with invalid access
to the private assignment operator of QSettings.
Reviewed-by: mgoetz
|
| | | |
|
|\ \ \ |
|
| |\ \ \ |
|
| | | | | |
|
| |/ / /
| | | |
| | | |
| | | |
| | | | |
Update the auto test for QTouchEvent to make sure the pressure is set to 1 for
Pressed/Moved/Stationary, but for 0 for Released.
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This enum indicates what kind of device generated the touch event
(TouchScreen or TouchPad). We use this information to control how touch
events are sent, specifically we restrict touch events to a single
widget/QGraphicsItem on touch-pads, since there is no direct
relationship between the physical touch location on the pad and the on-
using the touch-pad).
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
Conflicts:
src/gui/kernel/qapplication.cpp
|
| |\ \ \ |
|
| | | | | |
|
| |/ / /
|/| | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This introduces normalizedPos(), startNormalizedPos(), and
lastNormalizedPos() in QTouchEvent::TouchPoint, and must be set by the
implementation before being fed into Qt.
We are assuming and hoping that these functions will make it easier to
implement certain types of gestures (especially on a touchpad).
|
|/ / / |
|
|\ \ \
| |/ / |
|
| | |
| | |
| | |
| | |
| | |
| | | |
From 14 per X11 application down to 4.
Reviewed-by: jbache
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
By default this is set to false, meaning you will only get multitouch
events. The reason why this is important is that we use the first
touch of a new touch sequence to find out which widget to send
the subsequent touches to. And on a touchpad, you normally want
this to be the widget under the cursor when more than one finger
is pressed on the pad.
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
After a lot of thinking, the conclusion is that we really need to
to this. Lets see if we can add a flag to control it next.
|
| | |
| | |
| | |
| | |
| | |
| | | |
As documented in the Windows 7 SDK RC, the id's may not be reused. We
don't want the touchInputIDToTouchPointID hash to grow indefinitely, so
clear it each time we detect that all touch points have been released.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
... and not the screenRect
|