| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
- .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
|
| | |
|
| |
| |
| |
| | |
Also slightly updated a demo
|
| |
| |
| |
| |
| |
| |
| | |
Directly put a QRingBuffer from one QRingBuffer to
another QRingBuffer.
Reviewed-by: Thiago Macieira
|
| |
| |
| |
| |
| | |
Merge-request: 604
Reviewed-by: Marius Storm-Olsen <marius@trolltech.com>
|
| |
| |
| |
| |
| |
| |
| | |
NT 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>
|
|\ \
| |/ |
|
| |
| |
| |
| | |
Reviewed-by: Thiago
|
| |
| |
| |
| |
| |
| |
| |
| | |
In QTime::currentTime(), the pointer to the tm structure was used
without being initialized.
Task-number: 256889
Reviewed-by: Markus Goetz
|
|\ \
| |/ |
|
| |
| |
| |
| |
| |
| | |
The path /lib/ld-linux.so.2 is correct for i386 only, possibly some
other archs. But on x86-64, it's usually ld-linux-x86-64.so and it can
be in either /lib or /lib64.
|
| |
| |
| |
| |
| | |
These four enum values are used in variables of type Section, but aren't in it.
With gcc 4.4, it displays a warning that the value is lower than the lowest value
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
(ThreadEngineBarrier was implemented in the header as ThreadEngineSemaphore
in Qt 4.4 and Qt 4.5, and exported for a brief time in the Qt master branch. )
Unfortunately the inline call to acquire means that applications compiled
with Qt 4.4. and Qt 4.5 will contain a copy of the old implementation.
This is BC as long as the memory layout of the ThreadEngineBarrier class
stays the same, which means that we keep the QMutex member variable.
The old version of acquire will no longer be thread-safe since the new
version doesn't lock the mutex, but this is fortunately not a problem;
the only place it's called is in startAsynchronously() before the worker
threads are started.
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
There's no need to have separate cast-checker functions, plus the cast-
and centralise the function to create the object.
Reviewed-by: TrustMe
|
|\ \ \
| |/ / |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
These expressions aren't used anywhere yet, but I am sure we will find
use for them very soon now. I checked the compiler manuals for the
three commercial Unix compilers to verify which versions support these
macros.
Reviewed-by: Bradley T. Hughes
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If it was shared and you then set it back to an int type,
it is still marked as shared,. This might even lead to crashes.
The patch was sent through gitorious by Jürgen Starek.
Note: autotest added as well
|
|\ \ \
| |/ / |
|
| |\ \
| | |/
| | |
| | |
| | |
| | |
| | | |
Conflicts:
src/3rdparty/webkit/VERSION
src/3rdparty/webkit/WebCore/ChangeLog
src/network/access/qnetworkreplyimpl.cpp
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Use the fully qualified classname at relevant places in the
moc-generated code. Also, QMetaObject::newInstance() needs to
strip the namespace part, since the constructor signatures
don't contain the fully qualified name.
Task-number: 246064
Reviewed-by: Simon Hausmann
|
| | |
| | |
| | |
| | | |
Reviewed-by: Trust Me
|
|\ \ \
| |/ / |
|