| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
|
|
| |
Input methods didn't work properly wor widgets inside QWizardPage
because the widget got focus before it was shown and input context
wasn't initialized properly. The fix is to postpone
qinputcontext->setFocusWidget call until the widget is created (input
context will be initialized in the QWidget::create_sys function).
Task-number: 244604
Reviewed-by: Prasanth Ullattil
|
|
|
|
| |
Reviewed-by: TrustMe
|
|
|
|
|
|
|
|
| |
Before, we returned 0 for many interfaces because we picked up the IPv6
address regardless whether it was 0 or not.
Reviewed-by: Prasanth Ullattil <prasanth.ullattil@nokia.com>
Task-number: 249312
|
|
|
|
|
|
|
|
|
| |
The showPopup() from a combobox triggers a crash. This happens only for
a combobox which dosen't accept focus and it has been recreated. This is
due to some invalid widget pointer stored in the input context.
Task-number: 249576
Reviewed-by: ddenis
|
|
|
|
|
|
|
|
| |
Details: Added a note to the description about using POSIX functions for converting between data types such as floats and strings
Task-number: 244600
Reviewed-by: Denis Dzyubenko
Reviewed-by: Geir Vattekar
|
|
|
|
|
|
| |
Details: Added comment about QT_NO_WARNING_OUTPUT and/or QT_NO_DEBUG_OUTPUT on http://doc.trolltech.com/4.5/qtglobal.html#qInstallMsgHandler
Review-by: Geir Vattekar
|
|
|
|
|
|
|
|
| |
Adding note about how comparing using 0.0 will fail, and
an example on how to do it.
Reviewed-by: David Boddie
Reviewed-by: Geir Vattekar
|
|
|
|
| |
Reviewed-by: Kavindra Devi Palaraja <kavindra.palaraja@nokia.com>
|
|
|
|
| |
Reviewed-by: Morten Engvoldsen
|
|
|
|
| |
Reviewed-by: Anders Bakken <anders.bakken@nokia.com>
|
|
|
|
|
|
| |
I messed up the cherry-pick merge and left one of these in.
Reviewed-by: TrustMe
|
|
|
|
|
|
|
| |
They only make sense under the assumption that there most of the time is
no transform. With Falcon this isn't really the case.
Reviewed-by: Tom Cooksey <thomas.cooksey@nokia.com>
|
|
|
|
|
|
|
| |
Use the format passed in to the function rather than detecting it again
based on hasAlphaChannel().
Reviewed-by: Tom Cooksey <thomas.cooksey@nokia.com>
|
|
|
|
|
|
|
|
|
|
| |
The crash was caused by out-of-bounds reading on the raster engine's
clipping structures since our size had changed size last lock.
This code makes sure the clipData structures are atleast as tall as the
current height of the paint device.
Reviewed-by: Tom Cooksey <thomas.cooksey@nokia.com>
|
|
|
|
|
|
|
| |
is not already running.
Task-number: 231513
Reviewed-by: TrustMe
|
|
|
|
|
|
|
| |
not as a rendering primitive.
Task-number: 183493
Reviewed-by: TrustMe
|
|
|
|
|
|
| |
Reported by a former Doc Manager.
Reviewed-by: TrustMe
|
|
|
|
|
|
|
|
|
|
| |
We need to protect some overridden type and that is done in
qmacdefines_mac.h, so just include that. To top this off, a
function has changed that was introduced in 10.5. In order to
use it properly, we would need to do lots of version checking
and shuffling between types and it seems like more trouble that
it's worth at the moment. We may have to do that in the future,
but we'll deal with that then.
|
|
|
|
|
|
|
|
| |
Handle cases where QProcess::start() and startDetached() are passed a
null, empty, or "invalid" program string instead of crashing.
Task-number: 247865
Reviewed-by: Andreas Aardal Hanssen
|
|
|
|
|
|
|
|
| |
We basically store the currentFileInfo and use another one to continue
moving into the dir.
Task-number: 247645
Reviewed-by: Olivier
|
|
|
|
|
|
|
|
| |
It's likely these OS's will show up before we are done with
4.5, so it is worthwhile to have these values here, so that both we
and other developers can do nice things with them.
Reviewed-by: Prasanth Ullattil
|
|
|
|
|
|
|
|
|
|
|
|
| |
PostScript print engines.
The PDF/PostScript does not support perspective transforms, so it has
to be emulated through our draw_helper() fallback. PostScript doesn't
support alpha blending, so all perspective drawing needs to be forced
through the alpha print engine.
Task-number: 249754
Reviewed-by: Samuel
|
|
|
|
| |
Reviewed-by: Samuel
|
|
|
|
|
|
|
|
|
| |
offsets not handled correctly
Now also removes negative timestamps.
Task-number: 249059
Reviewed-by: Justin McPherson
|
|
|
|
|
|
| |
Clipping for drawLines works fine. textureBrushes are now accelerated
Reviewed-by: TrustMe
|
|
|
|
|
|
|
| |
The code was looking for a 't' to detect GMT-nnnn. It should really be
checking for 'gmt'.
Signed-off-by: Thiago Macieira <thiago.macieira@nokia.com>
|
|
|
|
|
| |
Task-number: 223087
Reviewed-by: TrustMe
|
| |
|
|
|
|
|
|
| |
Use the right surface for locking/unlocking.
Reviewed-by: TrustMe
|
|
|
|
|
|
| |
s/QDirectFBSurface/QDirectFBScreen/g
Reviewed-by: TrustMe
|
|
|
|
| |
Signed-off-by: Peter Hartmann <peter.hartmann@trolltech.com>
|
|
|
|
| |
Signed-off-by: Peter Hartmann <peter.hartmann@trolltech.com>
|
|
|
|
|
|
|
|
| |
negative sign.
I don't know why, but this only triggers for the month of October
Signed-off-by: Peter Hartmann <peter.hartmann@trolltech.com>
|
|
|
|
|
|
| |
It's the logical time that matters, not the exact date representation.
Signed-off-by: Peter Hartmann <peter.hartmann@trolltech.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Test if we're not past the end of the array before we attempt to read it.
Dates without timezone information are taken to be UTC, so merge the code.
If the date parsing failed, don't add a malformed cookie. Better to
have no cookie than to have it for past its expiration date.
Also update the autotests, since we now can cope with some of the
invalid cookies seen on the net.
Signed-off-by: Peter Hartmann <peter.hartmann@trolltech.com>
|
|
|
|
|
|
|
|
|
| |
then only allowing the three date formats that are in the rfc allow a much wider set of date strings. Because many browsers support this many websites send dates strings that are not in the rfc format.
See documentation in parseDateString for more details about the implementation.
Signed-off-by: Thiago Macieira <thiago.macieira@nokia.com>
Signed-off-by: Peter Hartmann <peter.hartmann@trolltech.com>
|
|
|
|
|
|
| |
Make sure that we can handle two Set-Cookie headers.
Signed-off-by: Peter Hartmann <peter.hartmann@trolltech.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
in the date and to differentiate between multiple cookies. When there are multiple set-cookie headers rather then combining them with ', ' use '\n' like Firefox because we are 100% sure that we have multiple cookies and using , can result in cases where the , is interpreted as as part of the date such as the following
set-cookie:a=b; expires=2009 mar 10
set-cookie:c=d
Combined the old way they result in the second cookie being ignored
a=b; expires=2009 mar 10, c=d
Using '\n' moves our cookie parser closer to Firefox's algorithm which
will result in more behavior and bug for bug compatibility.
Attempting to be smarter about the , will result in incompatibility
with Firefox's implementation (as my first attempt at fixing this bug
resulted).
Also when parsing multiple cookies when we have an error
don't return an empty list of cookies, but return the list of
cookies we were able to parse successfully so far.
Signed-off-by: Thiago Macieira <thiago.macieira@nokia.com>
Signed-off-by: Peter Hartmann <peter.hartmann@trolltech.com>
|
|
|
|
|
|
|
| |
the location header will be used to determine where to go.
Signed-off-by: Thiago Macieira <thiago.macieira@nokia.com>
Signed-off-by: Peter Hartmann <peter.hartmann@trolltech.com>
|
|
|
|
|
|
|
| |
QNetworkReply::finished() signal is emited.
Signed-off-by: Thiago Macieira <thiago.macieira@nokia.com>
Signed-off-by: Peter Hartmann <peter.hartmann@trolltech.com>
|
|
|
|
|
|
|
|
|
|
| |
specifically match the behavior of Firefox which servers test against. - When updating the cache metadata don't update content-* headers - Don't lowercase headers names when updating them - Fixed a typo in QNETWORKACCESSHTTPBACKEND_DEBUG code
Originally seen on http://www.bibelbund.de/htm/99-4-306.htm where on
refresh the 304 will set the content type of text/plain.
Signed-off-by: Thiago Macieira <thiago.macieira@nokia.com>
Signed-off-by: Peter Hartmann <peter.hartmann@trolltech.com>
|
|
|
|
|
| |
Everything else capitalizes both the F and the B. s/Fb/FB/g
Reviewed-by: TrustMe
|
|
|
|
|
|
| |
qWarning and qFatal should be in Latin1.
Reviewed-by: Thiago
|
|
|
|
| |
Reviewed-by: TrustMe
|
|
|
|
|
|
|
| |
documentation and updated a diagram.
Task-number: 228201
Reviewed-by: TrustMe
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
DirectFB sets the alpha byte to 0 in RGB32 for all drawing operations.
The raster paint engine needs this padding byte to be 0xFF as it shares
some code paths with RGBA8888_Premultiplied. So, always fall back to
raster engine for draw operations.
This is really due to a bug in the raster paint engine (Tracked by task
184073), which should ignore the extra byte. Once this task is fixed,
this patch can probably be reverted.
Reviewed-by: Tom Cooksey
|
|
|
|
|
|
|
|
| |
qt_win_display() will always trigger an assert and should not be used
in the src/painting directory.
Task-number: 248266
Reviewed-by: Samuel Rødal <sroedal@trolltech.com>
|
|
|
|
|
|
|
|
| |
PRINTER is dependant upon the PICTURE feature in 4.5, since the
PDF and PS engines now uses the QAlphaPaintEngine internally.
Task-number: 248568
Reviewed-by: Samuel Rødal <sroedal@trolltech.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Cocoa actually has a nice feature that if you pass arguments on the
command-line, Cocoa will pass those along as Open events later. This is
probably how we should have handled things inside of Qt as it would have
unified the file opening code. Unfortunately, we can't turn back time on
this, so we need to prevent it because people probably aren't expecting
it (i.e., they expect to do the parsing themselves, and not to get
events later). This also means that we can send the event immediately
instead of posting it, because the race that we had before no longer
exists. We only do this check during launch time because that's the only
time we may get bitten by it (people usually only parse the arguments
once).
Someday, people may actually WANT this functionality though. When that
comes along, we should make it an application attribute.
Task-number: 249553
Reviewed-by: Richard Moe Gustavsen
|
|
|
|
|
|
|
|
|
| |
Seems that things are a little less transparent in 10.5 (and have a
blur). Getting the blur in is going to be difficult, but adjusting the
opacity will get us closer than we are now.
Task-number: 249364
Reviewed-by: Jens Bache-Wiig
|