| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
NT support
Merge-request: 604
Reviewed-by: Marius Storm-Olsen <marius@trolltech.com>
|
|
|
|
|
|
|
|
|
| |
support
Also, buffer sizes passed to Registry APIs were incorrect.
Merge-request: 604
Reviewed-by: Marius Storm-Olsen <marius@trolltech.com>
|
|
|
|
|
|
|
| |
Also remove many #ifdef UNICODE blocks
Merge-request: 604
Reviewed-by: Marius Storm-Olsen <marius@trolltech.com>
|
|
|
|
|
|
|
| |
support
Merge-request: 604
Reviewed-by: Marius Storm-Olsen <marius@trolltech.com>
|
|
|
|
|
|
|
| |
support
Merge-request: 604
Reviewed-by: Marius Storm-Olsen <marius@trolltech.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Also - Make winPeekMessage() & winPostMessage() obsolete
- FlashWindowEx, IsValidLanguageGroup functions no longer resolved
dynamically (available on >= Windows 2000)
- LoadIcon/LoadCursor -> LoadImage w/LR_SHARED for system
icons/cursors
- qsystemtrayicon_win: use Shell_NotifyIconGetRect if available
(Windows 7)
Merge-request: 604
Reviewed-by: Marius Storm-Olsen <marius@trolltech.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
These days we can easily get very long paths, so we should support
application paths as long as needed.
There was also a potention exploit in that if the path was MAX_PATH or
larger, the string would not be \0 terminated (see MSDN docs for
GetModuleFileName), and thus cause problems in QString::fromWCharArray().
Merge-request: 604
Reviewed-by: Marius Storm-Olsen <marius@trolltech.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
support
Also: QString::fromUtf16() -> QString::fromWCharArray()
WCHAR & TCHAR -> wchar_t
LPTSTR/LPCTSTR -> LPWSTR/LPCWSTR
Documentation update
Merge-request: 604
Reviewed-by: Marius Storm-Olsen <marius@trolltech.com>
|
|
|
|
|
|
|
|
|
|
| |
support
Also TCHAR -> wchar_t
LPTSTR/LPCTSTRs -> LPWSTR/LPCWSTRs
Merge-request: 604
Reviewed-by: Marius Storm-Olsen <marius@trolltech.com>
|
|
|
|
|
| |
Also changed qdoc not to warn about undocumented parameters
if the function is marked with the \reimp command.
|
|
|
|
|
| |
Merge-request: 787
Reviewed-by: Bjørn Erik Nilsen <bjorn.nilsen@nokia.com>
|
|
|
|
|
|
|
|
|
|
| |
wheel
The solution is to check the the current "entered item" hasn't change
also when the scrollbars change values
Task-number: 200665
Reviewed-by: janarve
|
|\ |
|
| |
| |
| |
| |
| |
| | |
when paths to the ActiveSync headers/libraries are not set up.
Reviewed-by: Michael Goddard
|
|/
|
|
| |
Reviewed-by: trustme
|
|
|
|
|
|
|
|
|
| |
When the focus is set on a QGroupBox with the policy NoFocus, the focus
should be propagated to one of the child if it accepts the focus. This
was failing because QWidget::focusWidget() returns the QGroupBox itself.
Task-number: 257158
Reviewed-by: Denis
|
| |
|
|\ |
|
| |
| |
| |
| | |
Task-number: 218935
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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: 253902
Reviewed-by: Thierry Bastian
|
| |
| |
| |
| |
| | |
Task-number: 256762
Reviewed-by: TrustMe
|
| |
| |
| |
| |
| | |
Task-number: 256818
Reviewed-by: Trenton Schulz
|
| |
| |
| |
| | |
Reviewed-by: mauricek
|
| | |
|
| |
| |
| |
| | |
Reviewed-By: TrustMe
|
| |
| |
| |
| |
| | |
Some of the more advanced tests will fail for non-obvious
reasons if these basic assumptions don't hold.
|
| |
| |
| |
| |
| |
| |
| |
| | |
On windows, if your default printer is not reachable it would take a
lot of time to fail to construct the print engine. During that time
the UI would be frozen on the splash screen.
Reviewed-by: ossi
|
| | |
|
| |
| |
| |
| | |
I also changed a bit the way the timer for the popup is working
|
| | |
|
|\ \
| |/ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
The windowDidResize notification now differentiates an internally
triggered resize from a user triggered resize.
Task-number: 256269
Reviewed-by: Norwegian Rock Cat
|
| | |
|
| |
| |
| |
| |
| |
| | |
The configuration option was not added to the Windows configure.
Reviewed-by: hjk
|
| |
| |
| |
| | |
Reviewed-by: Gareth Pethig
|
| |
| |
| |
| |
| |
| |
| | |
- case for QVariant::Bool in switch statement was missing
Task-number: 215511
Reviewed-by: TrustMe
|
| |
| |
| |
| |
| |
| | |
These variables are never used.
Reviewed-by: TrustMe
|
| |
| |
| |
| |
| |
| | |
We already do this in QDirectFBWindowSurface::scroll
Reviewed-by: TrustMe
|
| |
| |
| |
| | |
Reviewed-by: Thiago
|
| |
| |
| |
| |
| | |
Merge-request: 760
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@nokia.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| |
| |
| |
| |
| |
| | |
A few "fixes" to make that number go down..
Reviewed-by: Thiago Macieira
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Created a table showing the use of different data types in relations with different Qt-supported Databases. Also reviewed by
Task-number: 182851
Rev-by: Geir Vattekar
Rev-by: David Boddie
Rev-by: Bill King
|
| |
| |
| |
| |
| |
| | |
These two entries were not removed since the server was an OOP server
Reviewed-by: Prasanth
|
| |
| |
| |
| |
| |
| |
| | |
This was basically a problem with shadow builds not being able to
access the pixmap.
Reviewed-by:eskil
|
| |
| |
| |
| |
| |
| |
| |
| | |
Coverity was complaining because we were not checking the return
value of find() but instead using the pixmap handle to check the
result. This makes the call more consistent
Reviewed-by: mgoetz
|