- 20 May, 2013 - 24 commits
-
-
Oswald Buddenhagen authored
this was forgotten when the value lists were extended by a size hint. Change-Id: I6f9b55ed671224a9b8735c8d937f94aac4a73a42 Reviewed-by:
Daniel Teske <daniel.teske@nokia.com> (cherry picked from qtcreator/f24c9865306624c2fc150d4bd262a5c4d5a3689a) Reviewed-by:
Joerg Bornemann <joerg.bornemann@digia.com>
-
Orgad Shaneh authored
Task-number: QTCREATORBUG-7006 Change-Id: I3f599f92d03b6f9fdf65b12cf4090e28cc497fbd Reviewed-by:
Oswald Buddenhagen <oswald.buddenhagen@digia.com> (cherry picked from qtcreator/6e3af2bf2e2833e0ecbc9b366af8e06abd7ecf96) Reviewed-by:
Orgad Shaneh <orgads@gmail.com> Reviewed-by:
Joerg Bornemann <joerg.bornemann@digia.com>
-
Orgad Shaneh authored
Warnings came up using MinGW 4.4: * qmakebuiltins.cpp: 'QString windowsErrorCode()' defined but not used [...] Change-Id: I80827f7f740ff380f13cef96d6b43baaa7e179cb (cherry picked from qtcreator/0e13cf3faffc7463ae2bf535dfdb008202112cc4) Reviewed-by:
Orgad Shaneh <orgads@gmail.com> Reviewed-by:
Joerg Bornemann <joerg.bornemann@digia.com>
-
Daniel Teske authored
Some projects set TARGET or DESTDIR only in the build_pass Task-number: QTCREATORBUG-4273 Change-Id: I3673dd93b37b10102a0c1f1ce053e1aef8aaf53f Reviewed-by:
Oswald Buddenhagen <oswald.buddenhagen@digia.com> Reviewed-by:
Daniel Teske <daniel.teske@digia.com> (cherry picked from qtcreator/95169eb8e39c6f43b7e74fbb18d4db19a38b0124) Reviewed-by:
Joerg Bornemann <joerg.bornemann@digia.com>
-
Martin Smith authored
The brief attribute for a C++ property was being written after the <property> tag had been closed. This has been fixed by explicitlty writing the brief attribute for each XML tag that has a brief text to write. Task-number: QTBUG-31149 Change-Id: Ic3857b8fa50cfb84536b838771751d8b92ed590e Reviewed-by:
Friedemann Kleint <Friedemann.Kleint@digia.com> Reviewed-by:
Topi Reiniö <topi.reinio@digia.com> Reviewed-by:
Jerome Pasion <jerome.pasion@digia.com>
-
Topi Reinio authored
The .qdocconf file for Qt Print Support includes examples/widgets in its exampledirs, presumably because a few examples there have printing support. The documentation for these examples is not accessible from Print Support index/module pages, and qdoc prints a lot of warnings for them (missing images). There's only few dependencies to examples in Print Support docs. These are resolved by copying a code snippet to correct place, and removing \sa links from QAbstractPrintDialog. Task-number: QTBUG-31137 Change-Id: Iac20d151f93ac16449241c6ee85979781b26e607 Reviewed-by:
Jerome Pasion <jerome.pasion@digia.com>
-
Oswald Buddenhagen authored
implicit sharing together with 'mutable' is a time bomb. we need to protect the nameMap, because concurrent "reads" may try to insert into the hash, which would go boom. we need to protect the key/value of Hash objects, because while the refcounting is atomic, the d pointer assignments are not, which would also go boom. we can simply use a QMutex to protect the whole environment, because it is very cheap in the uncontended case. Task-number: QTBUG-30779 Change-Id: Iaad5720041ca06691d75eb9c6c0e1c120d4a7b46 Reviewed-by:
Olivier Goffart <ogoffart@woboq.com>
-
Richard Moe Gustavsen authored
The way we reported screen position (and normalized position) for touch events was just wrong. The old implementation did not take into account that a view could be anything else than a direct child of the window, which fails for many cases (e.g when using QGLWidgets). Nor did it take into account the status bar, which made it hard to push small buttons since the touch would always be slightly offset. This patch calculates the screen pos by converting the touch pos to window pos, and then subtract the application frame (that contains the size of the status bar). Change-Id: Ib7f5f6dcea3a611e1ed75d57fb4a4718564752f0 Reviewed-by:
Tor Arne Vestbø <tor.arne.vestbo@digia.com>
-
Rafael Roquetto authored
Change-Id: Ia00d0f32e7d552421cc230ffca25085ab0a3a31e Reviewed-by:
Andreas Holzammer <andreas.holzammer@kdab.com> Reviewed-by:
Sean Harmer <sean.harmer@kdab.com> Reviewed-by:
Thomas McGuire <thomas.mcguire@kdab.com>
-
Thiago Macieira authored
The optimisation done in cbaf52b0 for Qt 5.0 got the order wrong of the comparison. The queue must be sorted in decreasing priority order. But since higher numbers mean higher priority, that means the queue must be sorted in decreasing priority number order. Task-number: QTBUG-29163 Change-Id: Iaf3424b9bb445bf5c71518927f37253cead454f3 Reviewed-by:
Konstantin Ritt <ritt.ks@gmail.com>
-
Jan Arve Saether authored
QGraphicsItems are not accessible, and calling updateAccessibility() with a QGraphicsTextItem caused the accessibility framework to try to load a plugin for QGraphicsTextItem. Since that was not found, it dumped this on the console: "Cannot create accessible interface for object: QGraphicsTextItem" Task-number: QTBUG-29720 Change-Id: I4aaa08ee6e97f03617fa08da0c6ef35992efdebf Reviewed-by:
Giuseppe D'Angelo <giuseppe.dangelo@kdab.com>
-
Liang Qi authored
In JSON, any number is stored in double. We need to make sure we keep the maximum possible number precision for integer number. In IEEE 754 double format, the significand precision is 53 bits(52 explicityly stored). Autotest is included. qint64 and double work fine. Task-number: QTBUG-28467 Change-Id: I7f857671c50e4334e9329c778f9b4f090f490540 Reviewed-by:
Sune Vuorela <sune@vuorela.dk> Reviewed-by:
Thiago Macieira <thiago.macieira@intel.com>
-
Stephen Kelly authored
Change-Id: Ic6743e8adb8d386fabc20c17c47fd110a47201da Reviewed-by:
Thomas McGuire <thomas.mcguire@kdab.com>
-
Eskil Abrahamsen Blomfeldt authored
The hack to use the environment variable for turning off the mouse cursor is broken when running against Ministro, because Ministro does not pass the environment on. A better solution is to make it possible to turn the cursor in the EGLFS plugin off in the hooks instead. Task-number: QTBUG-30553 Change-Id: Id09b48c350d2c95de9bb174f7480cf0cd2bf8145 Reviewed-by:
Samuel Rødal <samuel.rodal@digia.com>
-
Giuseppe D'Angelo authored
Change-Id: I44b2b60e89a3312889101d7e5c305f4f7c18f7ae Reviewed-by:
Olivier Goffart <ogoffart@woboq.com>
-
Olivier Goffart authored
when the type is a pointer to a registerable 1 argument template type. Task-number: QTBUG-31002 Change-Id: Iac0d6b71b2b805a1876110a0781d02188083c4e5 Reviewed-by:
Stephen Kelly <stephen.kelly@kdab.com>
-
jian liang authored
Set ref count to zero in QLocalePrivate::create() to avoid QLocalePrivate object leaking. Change-Id: I8948c27d59b2038266ab04c6113610b9b4481b45 Reviewed-by:
Thiago Macieira <thiago.macieira@intel.com> Reviewed-by:
Lars Knoll <lars.knoll@digia.com>
-
Gatis Paeglis authored
Comparing to the Qt4 implementation, possibleKeys() should skip records where qtKeys are equal. Task-number: QTBUG-31132 Change-Id: I2fb073b4dc7291f909cce616f40f7c2491e7cf26 Reviewed-by:
Friedemann Kleint <Friedemann.Kleint@digia.com> Reviewed-by:
Samuel Rødal <samuel.rodal@digia.com> Reviewed-by:
Tobias Hunger <tobias.hunger@digia.com>
-
Olivier Goffart authored
When encountering code such as: X<a<b> moc does not have the mean to know if 'a' is a type or a variable, so the type parser currently assume that '<' always open a template parameter. (instead of being the operator<) The type parser do not care about the actual type, it just need to strip the string out. The problem is that then the whole rest of the file will be considered as the type. With this patch, we also stop the parsing at semicolon. The type will be wrong, but this allow the parser to recover and it will continue to look for more classes after this. (In other words, moc will no longer break if it encounter such construct in a header. But it will still not parse such types correctly if used within a Q_OBJECT class) Task-number: QTBUG-31218 Change-Id: I1fef6bc58493d7c00df72401c9ad55463b24eaa7 Reviewed-by:
Lars Knoll <lars.knoll@digia.com>
-
Ray Donnelly authored
... in mingw-using specs because msysgit doesn't provide install.exe and Windows doesn't care about Unix permissions anyway. Task-number: QTBUG-31147 Change-Id: Ic8032ca1a970ef41381852b6c5c372b805a124f1 Reviewed-by:
Oswald Buddenhagen <oswald.buddenhagen@digia.com> Reviewed-by:
Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@digia.com>
-
Jørgen Lind authored
Change-Id: Iaf04172aa4fce8d6b354c1c1fc3c376831ee8e91 Reviewed-by:
Andy Nichols <andy.nichols@digia.com>
-
Jørgen Lind authored
When Xcursor LoadCursor fails to find a cursor Task-number: QTBUG-27537 Change-Id: I46086c78c3d5bea3c39187dcc55b4774e58f5749 Reviewed-by:
Samuel Rødal <samuel.rodal@digia.com>
-
Jørgen Lind authored
Inspired by QMutexLocker Change-Id: I66e31091d2a006db3272b627567d95d3e0b1c4f9 Reviewed-by:
Samuel Rødal <samuel.rodal@digia.com>
-
Jørgen Lind authored
This allows you to easily retrieve properties in the XSETTINGS specification. It is also possible to add listeners to get notified when a specific property changes. XSETTINGS is lazy initialized, so it will not be instansiated before someone uses it. For now the intended use is a fallback for finding cursor theme Change-Id: Id47f0613f5876424cd47d721b40da17d3f63429e Reviewed-by:
Samuel Rødal <samuel.rodal@digia.com>
-
- 15 May, 2013 - 6 commits
-
-
Tor Arne Vestbø authored
We were setting the frame origin and content size as two separate steps. The frame origin was asynchronous, while the content size was synchronous. This resulted in the window visually jumping/moving, instead of applying the new geometry in one single step. We now set both in one go using setFrame, by manually calculating the frameRectForContentRect. This makes the whole process asynchronous. Task-number: QTBUG-31039 Change-Id: Iaba46106b9f200c707507f330fa801c99e2e7d89 Reviewed-by:
Gunnar Sletta <gunnar.sletta@digia.com> Reviewed-by:
Tor Arne Vestbø <tor.arne.vestbo@digia.com>
-
Liang Qi authored
Autotest is included. Task-number: QTBUG-31046 Change-Id: Ie549b59112f458de478294fa00443a3cf6898c85 Reviewed-by:
J-P Nurmi <jpnurmi@digia.com>
-
Gatis Paeglis authored
Task-number: QTBUG-30705 Change-Id: I6fa02807255d0abf74aa38e94662bbe3d9e642bb Reviewed-by:
Gunnar Sletta <gunnar.sletta@digia.com>
-
Oswald Buddenhagen authored
the fallback is to look in the install dir (which is the build dir when no -prefix is used), which doesn't work for a script in the source dir. amends 6b38524b Task-number: QTBUG-31131 Change-Id: If615ab4e3a2839b6b5be9bf6ef79d3f894b1748d Reviewed-by:
Fawzi Mohamed <fawzi.mohamed@digia.com> Reviewed-by:
Joerg Bornemann <joerg.bornemann@digia.com> Reviewed-by:
Mitch Curtis <mitch.curtis@digia.com> Reviewed-by:
Thiago Macieira <thiago.macieira@intel.com>
-
Jens Bache-Wiig authored
After Apple added the resize functionality to window borders, they stopped rendering the size grip in most apps. Hence we do not need to either. Since the status bar height depends on the status bar being there, we considered the safest option to keep it but make it hidden. Change-Id: Ida06e8f0de0f50d746a7d25bc5a472e22a370645 Reviewed-by:
Gabriel de Dietrich <gabriel.dedietrich@digia.com>
-
Gabriel de Dietrich authored
We permanently enable 'wantsBestResolutionOpenGLSurface' when creating an Open GL window/surface. We were enabling it once we would detect a high-dpi Cocoa backend, whitout ever turning it off. Leaving it 'on' on non-high-dpi displays should not change anything. Task-number: QTBUG-31000 Change-Id: I3d0c77f7b36f3c22dacd04a50fcc5a7d88af32c0 Reviewed-by:
Samuel Rødal <samuel.rodal@digia.com> Reviewed-by:
Gunnar Sletta <gunnar.sletta@digia.com>
-
- 14 May, 2013 - 8 commits
-
-
Stephen Kelly authored
Change-Id: I1d745adfbae371f8f1f76e954be98f4c2fd962e0 Reviewed-by:
Alexander Neundorf <neundorf@kde.org> Reviewed-by:
Stephen Kelly <stephen.kelly@kdab.com>
-
Jan Arve Saether authored
If the menu bar is subject to height for width (HFW) we should of course respect that, but in addition we should ensure that the HFW is within the minimum and maximum height. This also is consistent with how QGridLayout calculates the effective minimum row height. This fixes a regression because change 4780f94e391b5e881497c5228661dead turned QTabWidget into a proper height-for-width citizen, and when setting a QTabWidget as a menuwidget, the buggy codepath for HFW was suddenly hit in menuBarHeightForWidth(). Task-number: QTBUG-31057 Change-Id: I3c1bb8063c92d6eda7e9433e44f08967d8e1c43e Reviewed-by:
Paul Olav Tvete <paul.tvete@digia.com>
-
J-P Nurmi authored
Task-number: QTBUG-30990 Change-Id: I421d9169b592da2b468eceb9df4f3f7c6a06e8d6 Reviewed-by:
Friedemann Kleint <Friedemann.Kleint@digia.com> Reviewed-by:
Andreas Aardal Hanssen <andreas@hanssen.name>
-
Bjoern Breitmeyer authored
The error was introduced with 28ee554b Change-Id: If3e51227af3880496ef2da3a18835b36d65bad78 Reviewed-by:
Friedemann Kleint <Friedemann.Kleint@digia.com> Reviewed-by:
Oswald Buddenhagen <oswald.buddenhagen@digia.com>
-
Tor Arne Vestbø authored
With scrollbars enabled we would get two resize events when tiling the windows. First one with the expected viewport size, and then a second one with a bigger viewport when the QMdiArea calculated that the space it set off for scrollbars was not needed after all. Depending on whether or not the geometry propagation of the platform plugin was synchronous or not, we would get one or both of the events before evaluating the viewport size against the expected size, resulting in flakeyness, and an expected fail on OS X. We now explicitly disable the scrollbars during the test, and restore them for the latter test that verifies that scrollbars show up when the area is resized below the minimum size of the combined child widgets. This allows us to unskip the expected failure on OS X, and should make the test less flakey. Change-Id: Ief767456cfd79f5cd0bb0e220c40e5995674ff71 Reviewed-by:
Gabriel de Dietrich <gabriel.dedietrich@digia.com>
-
Andy Nichols authored
Instead of waiting for -drawRect to call -setView on the NSOpenGLContext, we go ahead and attempt to set the context as soon as possible. If it is indeed required that we call -drawRect first then will try to call -setView again during -drawRect with the new NSOpenGLContext. Change-Id: I33d9f2ba241b49e8cfa6c9156dd5bf5e4cc6b164 Reviewed-by:
Liang Qi <liang.qi@digia.com> Reviewed-by:
Gunnar Sletta <gunnar.sletta@digia.com>
-
Venu authored
The HTTPS links fail in Qt Assistant on Windows as the qt installation package includes qt libraries that are built without SSL support for legal reasons. Task-number: QTBUG-31073 Change-Id: I86909abadb1e8164749d924cc53ee05aa57f8f31 Reviewed-by:
Jerome Pasion <jerome.pasion@digia.com> Reviewed-by:
Karsten Heimrich <karsten.heimrich@digia.com>
-
Gunnar Sletta authored
Task-number: QTBUG-31078 Change-Id: Id7221db752c06fc94e55ae859615abb2642a139b Reviewed-by:
Friedemann Kleint <Friedemann.Kleint@digia.com>
-
- 13 May, 2013 - 2 commits
-
-
Oswald Buddenhagen authored
it was only meant to automatically support syncqt.bat, which is gone now. fwiw, invoking batch files from within msys Makefiles was broken to start with, as sh cannot directly run them. Change-Id: I435568c578ce79e46f4e230e985ca9a04b34ffff Reviewed-by:
Joerg Bornemann <joerg.bornemann@digia.com>
-
Oswald Buddenhagen authored
we never call it with an explicit extension, so this only complicates matters. Change-Id: Ib15180130359bb9575bf5dda564f8b817431618f Reviewed-by:
Joerg Bornemann <joerg.bornemann@digia.com>
-