| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
we should include qt_windows.h and not windows.h because we have to
define WINVER to 0x500.
|
|
|
|
|
|
|
| |
Letting qdoc output it automatically produces the wrong header
file name.
Task-number: 217268 210171 220664
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
Brought up by Andy. See perforce change 314809,
17b07e3ab6192b31f77fd2f126705b9ab53b3937. Related to task 221708.
Reviewed-By: Andy Shaw
|
| |
| |
| |
| | |
Task-number: 193615
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
mjansen reported on #qt-labs that this change crashes KDE applications
that were calling delete on their plugins.
It turns out that is also how QPluginLoader works, so the commit was a
bad idea to start with.
This reverts commit 4c7004122a858cd6d891efc7923ba11484fbf997.
Reviewed-by: Thiago Macieira
|
| |
| |
| |
| | |
Reviewed-by: Volker Hilsheimer
|
| |
| |
| |
| | |
Task-number: 214026
|
| |
| |
| |
| | |
Reviewed-By: hjk <qtc-committer@nokia.com>
|
| | |
|
| |
| |
| |
| | |
It tries to keep the semantics of QString::append(QByteArray) as much as possible.
|
| |
| |
| |
| |
| |
| |
| | |
This partially reverts 9a5b40a011bd1b15a67d83564af55011761f8ad9 for
the QIconvCodec.
Reviewed-by: hjk
|
| |
| |
| |
| | |
make compiler distinguishing both happy.
|
| | |
|
| | |
|
| |\
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
src/sql/drivers/ibase/qsql_ibase.cpp
tests/auto/q3sqlcursor/tst_q3sqlcursor.cpp
tests/auto/qsqldatabase/tst_databases.h
tests/auto/qsqldatabase/tst_qsqldatabase.cpp
translations/qt_ru.ts
|
| | |
| | |
| | |
| | |
| | |
| | | |
Reported via qt-bugs.
Reviewed-By: Peter Hartmann
|
| | |
| | |
| | |
| | |
| | | |
This is possible because we anyway use a Mutex to access the static
hash
|
|/ /
| |
| |
| |
| |
| |
| | |
omissions when qdoc is used in certain Windows environments.
Task-number: 256415
Reviewed-by: Trust Me
|
| |
| |
| |
| | |
and remove duplicate defines elsewhere.
|
|\ \ |
|
| | | |
|
|/ / |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- .ts file -> TS file
- .qm file -> QM file
- .ui file -> UI file
+ a handfull of typos I stumbled over
Merge-request: 802
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@nokia.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
unlike in an earlier attempt, ids are textual this time.
the developer is able to provide a template for the string. when lupdate
and lrelease are integrated into the build process, this makes it
possible to avoid a round-trip to a dedicated string designer during the
early development stage.
Requirement-id: QT-435
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fixes: corelib/kernel/qcore_unix_p.h:127: error: `O_CLOEXEC' undeclared
Some toolchains claim to provide glibc >= 2.4 but do not define
O_CLOEXEC.
An alternative fix might be to define O_CLOEXEC ourselves as we do
with some of the system call numbers.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Rewritten the api almost from scratch, making it simplier and more
flexible at the same time.
The current implementation will not have complex gseturemanager class
inside Qt, but the QGesture base class, which represents both a
gesture recognizer and a gesture itself with a set of properties. A
set of common gestures that can use used in third-party applications
(and in Qt itself internally) is supposed to be found in
qstandardgestures.h, and a base class for user-defined gestures is in
qgesture.h
Gesture implementation for Pan on Windows7 has also been added as a
reference implementation for platform gestures.
|
| | |
|
| |
| |
| |
| | |
That's what unistd.h uses: void* can receive any pointer, while char* can't
|
| |
| |
| |
| | |
also older MSVC
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
QSharedPointer"
This reverts commit fb51a10ee0451274a430227566ae26efb2ac4474.
Sorry, it didn't work. I can fix the MSVC error, but the problem is
that older GCC versions (4.2) fail with the following code:
template<typename T> struct Buffer
{
char buffer[128] __attribute__((aligned(__alignof__(T))));
};
The same works fine in GCC 4.4.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
are declared in this file.
The one-definition rule allows the forward declaration appearing below to
apply to code that was earlier. Therefore, if the compiler finds out
how to delete the object, we can allow a QSharedPointer of a forward-
declared-type.
This means the actual problem is just a warning with g++. To catch the
error, we need a separate .cpp file and I'd rather run this as an
external test.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
one go.
This avoids one memory allocation. Currently, we only support calling
the default constructors. I will *NOT* implement argument passing for
C++03. I will implement it with rvalue references for C++0x-capable
compilers.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This obviously only works for classes that derive from QObject. And
you must remember that QSharedPointer controls the QObject's lifetime,
not the QObject parent-child relationship.
Reviewed-by: dt
Reviewed-by: Bradley T. Hughes
|
| |
| |
| |
| | |
Reviewed-By: ossi
|
| |
| |
| |
| |
| |
| |
| |
| | |
Do the timeout handling the right and cross-platform way. The code
that was in QProcess worked only on Linux, where the kernel sets the
remainder in the returned timeval structure.
Reviewed-By: ossi
|
| |
| |
| |
| | |
Reviewed-By: ossi
|
| |
| |
| |
| | |
Reviewed-By: ossi
|
| |
| |
| |
| |
| |
| | |
system call
Reviewed-By: ossi
|
| |
| |
| |
| |
| |
| |
| | |
This ensures that we're calling the open64 version of this function as
well as handling the O_CLOEXEC flag and EINTR errors.
Reviewed-By: João Abecasis
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Most of these functions are from unistd.h and need to have a loop
around the actual call because the calls can be interrupted by a
signal delivery.
Some special calls (open, dup2, pipe) require an extra flag to support
thread-safe execution: the file descriptor must be created from the
operating system with the FD_CLOEXEC flag already set.
The O_CLOEXEC flag is specified in POSIX.1-2008, but the rest is
Linux-specific.
Reviewed-By: João Abecasis
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| |
| |
| |
| | |
Requirement: QT-457
|
|\ \
| |/ |
|
| |
| |
| |
| | |
Reviewed-by: trustme
|
| |
| |
| |
| |
| |
| |
| | |
This is related to the following fix:
70137e0601549af1056082cdfbb4f141c70befab
Reviewed-by: trustme
|