summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Autotest: add tests for method call errorsThiago Macieira2009-07-021-2/+103
|
* Autotest: make sure we create the QDBusInterface after the object exists.Thiago Macieira2009-07-021-9/+12
| | | | | | | | | The current code allows making calls to QDBusInterface objects that failed to introspect. It's technically a valid condition. You won't be able to connect to signals, get or set properties, but making calls was possible. I don't know if I want to keep this change in behaviour.
* Fix setting of complex/custom properties and error messages.Thiago Macieira2009-07-021-31/+136
| | | | | | | | | | | | | | | | Complex properties require demarshalling before passing on to QMetaProperty::write(). We can't pass on a QVariant containing an un-demarshalled QDBusArgument. So add a new function that does the decoding properly, as well as error checking. Also take the opportunity to properly check the interface name in the case of setting a property exported from the object itself (not an adaptor). Task-number: 240608 Reviewed-by: Marius Bugge Monsen
* Use an "int status" extra parameter in property reading/writing.Thiago Macieira2009-07-025-32/+71
| | | | | | | | | | | | | | | | | | When calling qt_metacall with the ReadProperty or WriteProperty, the data is on argv[0] like it was before, but now the QVariant itself is on argv[1] and there's an extra parameter in argv[2] which the meta code can use to indicate result. This allows QtDBus to process properties much more easily. In the case of property reading, we need to be able to modify the variant itself, because copying types when we don't have the data isn't very easy. As for setting, we need to be able to tell setProperty to return true or false depending on whether we succeeded in setting the property or not. Reviewed-By: Kent Hansen Reviewed-By: Marius Bugge Monsen
* Avoid revalidating message parameters.Thiago Macieira2009-07-026-31/+55
| | | | | | | | | | | This is a small performance improvement when making a call: we don't need to validate what we already know to be valid because we either designed it to be so or because we've already validated. The D-Bus library unfortunately validates again and there's nothing we can do about it. But we can avoid doing it twice in our own code. Reviewed-By: Marius Bugge Monsen
* Keep creation failure errors for QDBusAbstractInterface.Thiago Macieira2009-07-025-70/+116
| | | | | | | | | | | In case the object creation fails, set isValid to false. This will prevent any outgoing calls to be made with invalid information. In that case, lastError will never change either. This required adding a method to QDBusPendingCall, to be able to create one such object from an existing QDBusError. Reviewed-By: Marius Bugge Monsen
* Adapt the message-sending code to return error messages from theThiago Macieira2009-07-024-51/+104
| | | | | | marshalling code. Reviewed-By: Harald Fernengel
* Add support for error messages in the D-Bus marshaller.Thiago Macieira2009-07-022-14/+24
| | | | Reviewed-By: Harald Fernengel
* Add central validation code to QDBusUtil.Thiago Macieira2009-07-021-0/+68
| | | | | | | These tests are useful in QDBusMessage and QDBusAbstractInterface. It avoids having the same messages all over the place. Reviewed-By: Harald Fernengel
* Add some new error codes for indicating invalid D-Bus parameters.Thiago Macieira2009-07-022-2/+15
| | | | | | | I'm wondering if I should be adding com.trolltech.QtDBus stuff now. But since there's already one there, I don't see why not... Reviewed-By: Harald Fernengel
* Add a function to check if an interface is implemented by an object.Thiago Macieira2009-07-024-46/+51
| | | | | | | Also reorganise a bit, moving the function to create the interface name from an object's class name to qdbusmisc.cpp too. Reviewed-By: Trust Me
* add license headersOswald Buddenhagen2009-07-025-0/+205
|
* Doc: adding details to qmake docsMorten Engvoldsen2009-07-021-0/+19
| | | | | | | | | | Added documentation about the create_prl and link_prl to the CONFIG variable in the qmake manual Task-number: 165165 Rev-by: Geir Vattekar Rev-by: Volker Hilsheimer
* Tinyint is unsigned, force it to such.Bill King2009-07-021-1/+3
| | | | | Tinyint only supports 0-255, so mark it as unsigned despite sign flag, which have the time is inverted/wrong.
* Get more autotests passing/fixed up.Bill King2009-07-023-4/+21
|
* We still need to Flip in NO_WM modeAnders Bakken2009-07-021-1/+1
| | | | | | This ifdef was simply in the wrong place. Reviewed-by: Donald <qt-info@nokia.com>
* Make sure we check the right deviceAnders Bakken2009-07-011-2/+2
| | | | | | Also. Make sure to call QRasterPaintEngine::end() Reviewed-by: Donald <qt-info@nokia.com>
* Code cleanupAnders Bakken2009-07-011-48/+36
| | | | | | | Move the code from QDirectFBPaintEnginePrivate::(end|begin) into QDirectFBPaintEngine::(end|begin) Reviewed-by: TrustMe
* Sync with QtCreator.kh2009-07-014-10/+94
| | | | Reviewed-by: kh
* Sync with QtCreator.kh2009-07-011-9/+13
|
* Do not start Assistant without at least an empty page.kh2009-07-011-2/+5
| | | | | | | | Noticed while looking into task 256903, since in case there are no recent shown pages,we would start Assistant only showning the search. Task-number: 256903 Reviewed-by: kh
* Doc: clearifying docs - QProgressDialogMorten Engvoldsen2009-07-011-1/+1
| | | | | | Clearifying details on a warning about a function call (setValue()) Task-number: qtp 4.5Workarea
* Fixed the build on Windows after regenerating the unicode tables.Denis Dzyubenko2009-07-012-4/+4
| | | | Reviewed-by: trustme
* Doc: correcting typoMorten Engvoldsen2009-07-012-2/+2
| | | | | | Correcting typos Task-number: 257225
* Regenerated unicode tables after the fix in the generator.Denis Dzyubenko2009-07-012-6693/+6694
| | | | | | | This is related to the following fix: 70137e0601549af1056082cdfbb4f141c70befab Reviewed-by: trustme
* Fixed the license header that the unicode table generated uses.Denis Dzyubenko2009-07-011-8/+85
| | | | | | | Also made sure that the generated code will not have trailing whitespaces. Reviewed-by: Thiago Macieira <thiago.macieira@nokia.com>
* Improve QtHelp error reporting.Friedemann Kleint2009-07-011-2/+2
| | | | Reviewed-by: kh <qtc-committer@nokia.com>
* Document unified toolbar change with regard to full screen change.Norwegian Rock Cat2009-07-011-3/+4
|
* operator==() for Unicode properties was omitting one property, which ↵Chusslove Illich (Часлав Илић)2009-07-011-0/+1
| | | | | | | resulted in wrong choice of unique properties for characters 451-45f. Reviewed-By: Thiago Macieira <thiago.macieira@nokia.com> Reviewed-By: Denis Dzyubenko <denis.dzyubenko@nokia.com>
* Don assume QVariant::String data is going to always be unicode in QODBCDerick Hawcroft2009-06-301-1/+1
| | | | | | - as was not the case for the psqlODBC driver Reviewed-by: Bill King
* integrate linguist tool autotests into the qt testsuiteOswald Buddenhagen2009-06-30200-0/+6573
| | | | Task-number: 218935
* Fix Toolbars in unified toolbar looking bad Carbon w/Fullscreen changesNorwegian Rock Cat2009-06-301-2/+17
| | | | | | | | | | | | | | | 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
* Doc: Said which formats we support for a QIODevice driven MediaSourceGeir Vattekar2009-06-301-1/+6
| | | | | Task-number: 253902 Reviewed-by: Thierry Bastian
* Doc: Fixed a doc bug in QPlainTextEdit class description.Geir Vattekar2009-06-301-7/+7
| | | | | Task-number: 256762 Reviewed-by: TrustMe
* Doc: About menu on the Mac gets the application name from Info.plist.Geir Vattekar2009-06-302-3/+6
| | | | | Task-number: 256818 Reviewed-by: Trenton Schulz
* fix crash in QLocalServer on WinCE when waitForNewConnection times outJoerg Bornemann2009-06-301-1/+1
| | | | Reviewed-by: mauricek
* Doc: Fixed links that pointed to removed documentation.Geir Vattekar2009-06-301-3/+4
| | | | | | | | Information on issues with the icc compiler has been moved in the docs. Redirected links that still pointed to the old location. Task-number: 257039 Reviewed-by: Morten Engvoldsen
* Compile qmake autotestMarius Storm-Olsen2009-06-301-1/+1
|
* QWidget::adjustSize() sends a spontaneous event - Mac OS X CocoaPrasanth Ullattil2009-06-302-2/+12
| | | | | | | | The windowDidResize notification now differentiates an internally triggered resize from a user triggered resize. Task-number: 256269 Reviewed-by: Norwegian Rock Cat
* New binaryMarius Storm-Olsen2009-06-301-0/+0
|
* Support the -qtlibinfix parameter already on Unix/MacMarius Storm-Olsen2009-06-302-6/+15
| | | | | | The configuration option was not added to the Windows configure. Reviewed-by: hjk
* Remove links to out-of-date class chart.Jason McDonald2009-06-302-4/+0
| | | | Reviewed-by: Gareth Pethig
* bug fixDerick Hawcroft2009-06-301-0/+1
| | | | | | | - case for QVariant::Bool in switch statement was missing Task-number: 215511 Reviewed-by: TrustMe
* Remove unused variablesAnders Bakken2009-06-291-2/+0
| | | | | | These variables are never used. Reviewed-by: TrustMe
* Remove superfluous call to SetBlittingFlagsAnders Bakken2009-06-291-1/+0
| | | | | | We already do this in QDirectFBWindowSurface::scroll Reviewed-by: TrustMe
* QTemporaryFile: Report the user-provided openModeJoão Abecasis2009-06-292-1/+35
| | | | Reviewed-by: Thiago
* add Russian to the "'own' languages hack" until task #196275 will be closedRitt Konstantin2009-06-291-0/+1
| | | | | Merge-request: 760 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@nokia.com>
* Always turn on shadows for Cocoa.Norwegian Rock Cat2009-06-291-2/+1
| | | | | | | | | | | | 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
* QNetworkAccessManager stuff: Some fixes for coverityMarkus Goetz2009-06-293-6/+13
| | | | | | A few "fixes" to make that number go down.. Reviewed-by: Thiago Macieira
* Fix crash/artifacts on SuperHTom Cooksey2009-06-291-3/+3
| | | | | | | | | | | Add SuperH to the ever growing list of architectures which can't correctly dereference a short* which is not 16-bit aligned. Turning this into a white-list rather than a black list might make sense at some point, but as QT_ARCH_I386 isn't defined on windows, the white list looks even uglier at the moment. :-) Task-number: 257077 Reviewed-by: TrustMe
generated by cgit v0.12 at 2024-12-05 00:18:37 (GMT)