Change-Id: I91c5afc061e91c6088398d039c1c1fd3d79254ca
Reviewed-by: Morten Johan Sørvig <morten.sorvig@theqtcompany.com>

Change-Id: Iadaca71328404bd6c526af5095b32e5e35548182
Reviewed-by: Morten Johan Sørvig <morten.sorvig@theqtcompany.com>

Main use case is for KDE Plasma, which needs to know about real
window system coordinates. Can also be used by applications that
do all the scaling manually, and that do not want to have Qt
scale the coordinate systems and painters.

Change-Id: Ic595131c5e2fb4c0af95e9b5bd3e40beee86760b
Reviewed-by: Morten Johan Sørvig <morten.sorvig@theqtcompany.com>

Change-Id: I0fce05998ba6092c4dd1d64790c56c0668383477
Reviewed-by: Morten Johan Sørvig <morten.sorvig@theqtcompany.com>

Since we're making things look pretty :)

Change-Id: Ibc2e5f7315b9ecf789b8c7cdbf100632b9a2b4c0
Reviewed-by: Morten Johan Sørvig <morten.sorvig@theqtcompany.com>

Support cases where one or more screens have negative
positions.

Make the text size a (constant) fraction of the painted
screen rectangle height.

Change-Id: Iea39aa49281cfe2b97c3e9b2414ee5db6dfe1fbb
Reviewed-by: Paul Olav Tvete <paul.tvete@theqtcompany.com>

Mention if this is point or pixel sized text.

Change-Id: I9996bca8370e2822a14e8090b64da2d21b40e98e
Reviewed-by: Paul Olav Tvete <paul.tvete@theqtcompany.com>

QScreen's geometry is always determined by the platform screen,
since there is no Qt API to resize or move a screen. Therefore,
it makes no sense for the platform screen to ask QScreen for the
geometry.

Change-Id: Iedaa40e06e3a878f4e4e13fddd13a67a62d1f0f9
Reviewed-by: Morten Johan Sørvig <morten.sorvig@theqtcompany.com>

...just because we can.

Change-Id: I72fcb05711c3b5ecee250fdf0adfc0b8304590cb
Reviewed-by: Morten Johan Sørvig <morten.sorvig@theqtcompany.com>

Initialize the sliders to the currently active factors.

...and fix up the layout so the sliders align properly,
and aren't squashed when resizing.

Change-Id: I37ef853b0fd5a26939134da7116778f898f52a88
Reviewed-by: Morten Johan Sørvig <morten.sorvig@theqtcompany.com>

Change-Id: Ic312bff631380fa5b40b927b092eb17940026b94
Reviewed-by: Morten Johan Sørvig <morten.sorvig@theqtcompany.com>

Assume that the logical DPI for the primary screen is sane, and
keep font sizes constant as screens are scaled. The global scale
factor will act as a zoom level, and will cause all fonts to be bigger.

Note that since we do not change logicalDpi after application startup,
the manual test sliders will not match what happens
with auto scaling. We may want to fix that...

Change-Id: I5a3daa57c2dacf0158836492d31573723e49399a
Reviewed-by: Morten Johan Sørvig <morten.sorvig@theqtcompany.com>

We don't want to turn off font hinting based on whether auto-scaling is on,
otherwise Qt Creator will look bad on a low-DPI screen. Instead, we turn it
off only if we have at least one screen that is scaled.

QHighDpiScaling::isActive() now means that there is actual scaling going on.
There is currently no need for the old meaning, so this change does not include
QHighDpiScaling::isEnabled().

Note that nothing can save us from the case where there is one high-DPI and
one low-DPI screen.  In that case we choose looking bad on the low-DPI screen
instead of looking like crap on the high-DPI screen. Also note that our font
system we doesn't allow us to change our minds on hinting later when screens
are plugged in or removed.

Change-Id: I14a4ec7a49f4ba74a4c74684c7b951d0a71b951d
Reviewed-by: Morten Johan Sørvig <morten.sorvig@theqtcompany.com>

QBasicDrag does not have enough information to map the
coordinates, so we move that responsibility to the plugin.

Change-Id: I6eb87014b3259844bb3373ecf961d92debdb2b84
Reviewed-by: Morten Johan Sørvig <morten.sorvig@theqtcompany.com>

This is a seriously dirty hack, but without
this, screen geometries will be wrong when scale
factors are changed after application startup.

Change-Id: Ia39164303ef648ec3752d7f4b9db06477a2d3fb4
Reviewed-by: Morten Johan Sørvig <morten.sorvig@theqtcompany.com>

Change-Id: I24e019a4a960425028c982dcc94d82643c836003
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@theqtcompany.com>
Reviewed-by: Morten Johan Sørvig <morten.sorvig@theqtcompany.com>

Move to the class documentation in the cpp file,
focus on documenting the class and not necessarily
high-dpi scaling in general.

Change-Id: I4f04398904325b2f9061db8d3a82cd362276e977
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@theqtcompany.com>
Reviewed-by: Paul Olav Tvete <paul.tvete@theqtcompany.com>

Bring back static versions of the constrained scaling functions.

To be squashed with dbe2dd29

 .

Change-Id: Id05b8085ab56dd777ce1ab3b7da3ce47c01dcb00
Reviewed-by: Morten Johan Sørvig <morten.sorvig@theqtcompany.com>

Add a function to determine the closest acceptable geometry
(height-for-width) to QPlatformWindow similar to the existing
QPlatformWindow::windowMinimumSize(), windowMaximumSize()...
Clean up the hack in the Windows platform plugin accordingly.

Change-Id: I96e943cfdbafdd0ff444e0d53ee0bdf8603d33df
Reviewed-by: Paul Olav Tvete <paul.tvete@theqtcompany.com>

Use QTestLib instead, which will handle the QHighDpi
coordinate scaling.

Change-Id: Ib2ab9c6edfa6ffbf594ab6251c4b0b83f9581d6c
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@theqtcompany.com>

platformScreenForWindow() is currently implemented as:
	return window->screen()->handle();

Use window.screen() directly and avoid the QHighDpi
conversion call.

Change-Id: I0f6487efc4d1494813179665b21150f3ca7a8666
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@theqtcompany.com>
Reviewed-by: Paul Olav Tvete <paul.tvete@theqtcompany.com>

Conflicts:
	src/gui/kernel/qsimpledrag.cpp
	src/gui/kernel/qwindowsysteminterface.cpp
	src/gui/kernel/qwindowsysteminterface_p.h
	src/plugins/platforms/xcb/qxcbwindow.cpp

Change-Id: Icd887552ade61d6a2b2527383970f7145aa00faf

So they can be used in QtQuickTest.

Change-Id: I64925feb243fb27234951276d81119bc1f6d5a56
Reviewed-by: Simon Hausmann <simon.hausmann@theqtcompany.com>

Change-Id: I4ed8872ecd560d51c00cb3d2b93e082c5abdd8dc
Reviewed-by: Olivier Goffart (Woboq GmbH) <ogoffart@woboq.com>
Reviewed-by: Marc Mutz <marc.mutz@kdab.com>

This enables users to construct enum values from strings
and provides useful qDebug operators.

Task-number: QTBUG-10777
Change-Id: Ia3592f00d559b980b4875ee8fb5e8ffb4328d464
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@theqtcompany.com>
Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>

Change a21dfab5

 de-inlined its
destructor, so, the class needs to be exported.

Change-Id: I32d21622a944a93718f549060e5e5f7e71fd2646
Reviewed-by: Simon Hausmann <simon.hausmann@theqtcompany.com>

Add missing equal sign to have the result of the OR
stored inside the modifiers variable.

Fixes Coverity CID#89071.

Change-Id: I0ee1a080f5f6757ae7646733aa3bb5cf8c6cdeed
Reviewed-by: Simon Hausmann <simon.hausmann@theqtcompany.com>

QMap::empty() does not empty the list but is the STL
version to ask if the map is empty. Remove the comment
and code as operator>> of QDataStream will clear the
map.

Fixes Coverity CID#89073

Change-Id: I259e518b44afd42b698368b42aedcc3b84240aca
Reviewed-by: Simon Hausmann <simon.hausmann@theqtcompany.com>

Change-Id: I66f49c6db82eadc3b11cc9b1cf01375e9596a8e6
Reviewed-by: Lisandro Damián Nicanor Pérez Meyer <perezmeyer@gmail.com>
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@theqtcompany.com>
Reviewed-by: Mark Brand <mabrand@mabrand.nl>

Change-Id: Iaa953df941d888b8ae1a590dd728a1d819d7e604
Reviewed-by: Konstantin Ritt <ritt.ks@gmail.com>
Reviewed-by: Mark Brand <mabrand@mabrand.nl>

Change-Id: I05f156faae85abe11edc954dd358ddfcfd320c74
Reviewed-by: Simon Hausmann <simon.hausmann@theqtcompany.com>

Change-Id: I2f5d6e37e630d70c4ba3ae81e807a89c447c8b26
Reviewed-by: Simon Hausmann <simon.hausmann@theqtcompany.com>

Don't hit the scrollbar with the mouse click

Change-Id: Ie82d8c5c058df9a482e7d5de2fe40681572f19ad
Reviewed-by: Simon Hausmann <simon.hausmann@theqtcompany.com>

make sure it'll work with the new mouse handling as well.

Change-Id: Ia2d567e618b77b0fa3532ee6c335cbdf5e496241
Reviewed-by: Simon Hausmann <simon.hausmann@theqtcompany.com>

Change-Id: I8950a3eb9792dff90ed64cd3bf1d572745b05886
Reviewed-by: Simon Hausmann <simon.hausmann@theqtcompany.com>

Add command line options for
- Grabbing gestures
- Suppressing mouse and touch events

Add gesture events to the log.
Add a hierarchy of gesture classes storing the parameters
of finished gestures with drawing functionality and
implement for pan and swipe.

Task-number: QTBUG-46195
Change-Id: I019fe5b60116316a54e11b2c30e1d34f5e72bcf0
Reviewed-by: Shawn Rutledge <shawn.rutledge@theqtcompany.com>

This helps qdoc's parser.

Change-Id: I4c7f2dff348b87659c93ddb14d012d5bf2e626f2
Task-number: QTBUG-46498
Reviewed-by: Topi Reiniö <topi.reinio@digia.com>

Bring back code from the DPR scaling.

To be squashed with dbe2dd29

 .

Change-Id: I14dc868abf80c75f58b952c8636dd786e78fbd7c
Reviewed-by: Paul Olav Tvete <paul.tvete@theqtcompany.com>

Pass on the requested delay into the mouse events. We don't care about
single msecs as the surrounding code also takes time that we don't
consider and whenever we generate a release we add 500ms of time skew
anyway.

The initial press of a double click has to increment the timestamp,
just like all other mouse events do.

Change-Id: Ifb94830f9f878ce87d92bfd86c72a16b55052f3b
Reviewed-by: Simon Hausmann <simon.hausmann@theqtcompany.com>
Reviewed-by: Lars Knoll <lars.knoll@digia.com>

HtmlGenerator::highlightedCode() contained a potential
out-of-range- memory reference, which is prevented by
this fix.

Change-Id: I3bc87a8287e1d51c2786f5ec42384dbac04c9636
Task-number: QTBUG-45643
Reviewed-by: Martin Smith <martin.smith@digia.com>