| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
This is probably more correct, but is also the way it used to behave.
|
|
|
|
|
| |
Also it should be executed a little later to avoid accidental behaviour
changes.
|
| |
|
| |
|
|
|
|
|
|
| |
createStandardContextMenu should still only cut/copy in normal echo mode
and the Qt3Support function validateAndSet will again only set if it is
validated.
|
|
|
|
|
| |
It was accidentally left commented out instead of working with
QLineControl.
|
|
|
|
|
|
| |
QAbstractSpinBox had some code using QLineEdit internals, this had to
be move to use QLineControl as well.
This commit also includes fixing some typos in my last commit.
|
|
|
|
|
| |
Didn't notice there were still some TODO markers left. They have now all
been done.
|
|
|
|
|
| |
This change to QLineEdit didn't merge, as it needs to be applied to
QLineControl in this case.
|
|
|
|
|
|
|
|
|
|
| |
Splits out the control logic of QLineEdit into QLineControl, which is
somewhat similar to QTextEdit. This was originally worked on in the
ianws-qt-lineedit-textedit-research repository, and then further
developed in kinetic in the kinetic-declarativeui-qfxlineedit branch.
Note that this also includes a tiny change to qvalidator.h which allows
validators to be used in qml.
|
|
|
|
| |
Task-number: 257118
|
| |
|
|
|
|
| |
Task-number: 162945
|
|
|
|
| |
This was not supported before by MSVC6 and MSVC2002
|
|
|
|
| |
removing foreach seems to help on Windows
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
- .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
|
|
|
|
|
|
|
|
|
|
|
| |
If a big widget is inside a scroll area, and this widget is in the
limits of XCOORD_MAX, its child might not be inside the limits.
The child is then limited to wrect, but wrect might not be on the
screen because the parent is scrolled. To avoid this problem,
the widgets position should not influence whether wrect is used or not.
Task-number: 144779
Reviewed-by: nrc
|
|
|
|
|
|
|
| |
On Mac OS X, QMenuBar::clear() does not remove menu items
that have been merged into the system menu bar.
Task-number: 255222
|
|
|
|
| |
Task-number: 256452
|
|
|
|
|
|
| |
Simplified caching of uniform locations.
Reviewed-by: Samuel
|
| |
|
|
|
|
|
|
|
| |
We used to check the 100 first sections and 100 last sections
Now we make sure we check 100 visible sections
Task-number: 255574
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This happens only for widgets with focus frames. Since the mouse
location at the time of this event will be outside of the focus frame,
we cannot use it to identify the widget. Instead, use the QDragManager's
currentTarget() to deliver the drag leave event.
Task-number: 252088
Reviewed-by: Norwegian Rock Cat
|
| |
| |
| |
| |
| |
| |
| |
| | |
Since we don't support Windows versions < Win 2000, we can just
go ahead and replace usage of the old compat dialog.
Task-number: 222417
Reviewed-by: Prasanth
|
| |
| |
| |
| |
| |
| | |
Without this, QWindowSurface::flush() doesn't work.
Reviewed-by: Samuel
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Even though the _XEMBED_INFO property uses 32 bit values,
prop_return has 64-bit padded values in 64-bit applications,
see man XChangeProperty. Without this fix the XEMBED client
will read XEMBED_MAPPED wrong and unmap (hide) itself.
Merge-request: 797
Reviewed-by: Denis Dzyubenko <denis.dzyubenko@nokia.com>
|
| |
| |
| |
| |
| |
| | |
HoverEnter/Leave now do nothing.
Task-number: 256103
|
|/ |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
With document margins, the mapping from content-coordinates to visual
coordinates went wrong.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
| |
For example when an unhandled key sequence (i.e. that has now shortcut
assosiated with it) like Alt-L is pressed, we shouldn't insert the 'L'
text from the QKeyEvent::text() into the text widget.
Reviewed-by: Thomas Zander
|
| |
|
|
|
|
| |
That's what unistd.h uses: void* can receive any pointer, while char* can't
|
|
|
|
|
|
| |
account for all sections is sorting is enabled.
Task-number: 208320
|
|
|
|
| |
also older MSVC
|
|
|
|
| |
SOCK_CLOEXEC
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
The SOCK_NONBLOCK, SOCK_CLOEXEC and accept4(2) calls are
Linux-specific. Other platforms get the same behaviour through
emulation.
Reviewed-By: ossi
|
|
|
|
|
|
|
| |
I think I found two file descriptor that aren't closed. One seems like
a genuine leak, the other seems intentional.
Reviewed-By: ossi
|