| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
Reviewed-by: TrustMe
|
| |
|
|
|
|
|
|
|
| |
This test handles the case when one limits the size of the socket's
read buffer and more data than the buffer size is available.
Reviewed-by: ossi
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In the following configuration, wrect was off-screen and the widget was
not painted:
-scroll area "A"
-contains another scrollarea "B" with 2*WRECT_MAX < size < XCOORD_MAX
-the widget contained in B has size > XCOORD_MAX
-A is scrolled to the the bottom
To fix the issue, wrect is moved to the area where the top level window
is in the widget coordinate.
Task-number: 144779
Reviewed-by: nrc
|
|
|
|
| |
Task-number: 246999
|
|
|
|
| |
Error messages and __postInit__.
|
|
|
|
|
|
|
|
|
| |
Unfortunately the codepath for keyPressEvent does not call updateState,
so we have to add the same line in two places.
Note that updateState() is only called from mousePressEvent() and
mouseMoveEvent().
Task-number: 254053
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Setting the current font would change the current font and then it
would try to select the right model index and get the font only from
the text of the combobox. This was resetting the point size of the font,
resulting in emitting the signal a second time.
In the case of the user, it was also causing signals to be called in
a loop.
Task-number: 229731
|
|/
|
|
|
|
| |
The qhelpgenerator auto test was also updated to test the new feature.
Reviewed-by: kh
|
|
|
|
|
|
|
|
|
|
|
| |
- .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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch improves the graphics view support for input
methods in several ways:
* A new ItemAcceptsInputMethod flag is introduced to serve
the same purpose for graphics items as WA_InputMethodEnabled
does for widgets: Input method support can be controlled
individually for each item.
* The input method sensitivity of a view (i.e. the value of
the WA_InputMethodEnabled flag) is updated dynamically
whenever the input method support of the current focus
item may change.
* Input contexts are reset whenever an item that supports
input methods loses focus.
Reviewed-by: janarve
Task-number: 254492
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
with QDBusInterface.
The problem was that I didn't know how to implement the operator= for
all types. But it turns out that this was possible all along: the only
types I have to implement the operator= for are the basic types, which
are already demarshalled.
The complex types are left in QDBusArgument semi-demarshalling, but we
have QDBusMetaType::demarshall, which takes a void* to an
already-constructed type and demarshalls into it. That's exactly what
the doctor ordered.
Task-number: 206765
Reviewed-By: Marius Bugge Monsen
|
| |
| |
| |
| |
| |
| |
| |
| | |
QDBusAbstractInterface.
They're now good enough and as fast.
Reviewed-By: Marius Bugge Monsen
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| |
| |
| | |
marshalling code.
Reviewed-By: Harald Fernengel
|
| |
| |
| |
| | |
Requirement: QT-457
|
|\ \
| |/ |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
The problem is that when restarting, the time is at the end. So the
current value changes to the end value instead of the initial value.
|
| |
| |
| |
| |
| |
| |
| | |
Fixed inheritance of stroke attributes, the font-size and text-anchor
attribute. Autotest added by Kim.
Reviewed-by: Kim
|
| |
| |
| |
| |
| | |
Merge-request: 604
Reviewed-by: Marius Storm-Olsen <marius@trolltech.com>
|
| |
| |
| |
| |
| | |
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 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
|
| |
| |
| |
| |
| | |
Some of the more advanced tests will fail for non-obvious
reasons if these basic assumptions don't hold.
|
|\ \
| |/ |
|
| | |
|
| |
| |
| |
| | |
Reviewed-by: Thiago
|
| |
| |
| |
| |
| |
| |
| | |
This was basically a problem with shadow builds not being able to
access the pixmap.
Reviewed-by:eskil
|
| |
| |
| |
| |
| | |
Task-number: 217003
Reviewed-by: Bill King
|