| Commit message (Collapse) | Author | Age | Files | Lines |
|\ |
|
| |\ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
On the undo/redo stack, it needs to be treated as a separate command
Task-number: QTBUG-5786
Reviewed-by: ogoffart
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
On Mac OS X, with a QLineEdit, QKeySequence::MoveToStartOfBlock should
move the cursor to the beginning of the input, and
QKeySequence::MoveToEndOfBlock to the end of the block
Same for selection. The shortcuts also had to be updated.
Task-number: QTBUG-4679
Reviewed-by: Olivier Goffart
|
|/
|
|
|
|
|
|
| |
On the Mac Up/Down arrow keys move the cursor to the beginning/end of the
lineedit. The fix is to make sure the corresponding keyevent will be accepted
by the QLineEdit and not propagated to parent widgets (resulting in a beep).
Reviewed-by: Prasanth
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Qt key event was not handled properly in the case of long key press.
With long key press, QCoeFepInputContext::commitCurrentString gets
called 3 times("q", "", "1"). (Normal key press is causing one call).
This is how aknfep works, so commitCurrentString was modified
to replace first character if long key press event detected.
E.g. "q" is replaced with "1".
qlinecontrol modified to keep cursor position correct.
Signed-off-by: axis <qt-info@nokia.com>
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Previously we didn't update the editor contents if the new preedit
string was empty. However, it could be empty because the user just
erased it, so the bug was fixed by checking whether the preedit
string in the event and in the editor are different.
RevBy: Denis Dzyubenko
|
|\ \
| |/ |
|
| |
| |
| |
| |
| |
| | |
However, compiling with QT_NO_ICON will still not work :(
Reviewed-by: tom
|
|/
|
|
|
|
|
|
|
| |
When echo mode was set to PasswordEchoOnEdit in a QLineEdit, and its text
selected, pressing the return key would erase the text and start editing it
instead of validating the password. Auto-test included.
Reviewed-by: Olivier
Task-number: QTBUG-4401
|
|
|
|
|
|
|
| |
The bug against QFxTextInput is actually due to a bug in QLineControl.
Task-number: QT-2319
Reviewed-by: Martin Jones
|
|
|
|
| |
Reviewed-by: Trust Me
|
|
|
|
| |
Reviewed-by: Trust Me
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
examples/opengl/samplebuffers/glwidget.cpp
src/corelib/io/qfsfileengine_unix.cpp
src/corelib/kernel/qobject.cpp
src/corelib/tools/qsharedpointer.cpp
src/gui/gui.pro
tests/auto/qhttp/tst_qhttp.cpp
tests/auto/qkeyevent/tst_qkeyevent.cpp
|
| |
| |
| |
| | |
Reviewed-by: Trust Me
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
| |
When selecting the text and setting the cursor position, we need to
emit the cursorPositionChanged signal. This seems to be a copy-paste
error from refactoring QLineEdit, as the function call is there in the
original version of setSelection(). The effect was two test breakages
in tst_QDateTimeEdit, because the section and cursor position of the
QDateTimeEdit would be out of sync.
Reviewed-by: Gunnar
|
| |
|
|
|
|
| |
Reviewed-by: Trust Me
|
|
Manually merged from the kinetic repository, where it has been used
for a while. Like QTextControl, there is no auto test for the control,
just for the widgets built with it.
The purpose of this change is so that we can build stuff like QLineEdit
in other places (like kinetic). Also included is a trivial change to
QValidator, needed to use it with QLineControl in QML.
Reviewed-by: mbm
|