| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently splitview support is defined in exported global private method.
There is no guarantee that input context is created, or updated when
the API is called. This is problematic, since the client need to find
a correct place and time when to call the API.
As a change, update existing input context when the API is called.
Also, take into account the splitview flag when updating input context.
This ensures that client can enforce the flag use correctly.
Task-number: QTBUG-18715
Reviewed-by: Guoqing Zhang
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Do windowstate change to fullscreen inside updateEnabled(false) -
updateEnabled(true) guard block to avoid flickering of screen
area, when keyboard opens in splitview.
In worst case, screen is drawn three times:
- resize the content area to fit into splitview
- change windowstate to fullscreen
- ensure visibility of the focusitem by scrolling the view
Now, all these happen inside one "update".
Task-number: QTBUG-18737
Reviewed-by: Guoqing Zhang
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When splitview is open and user long taps an text input item,
a context menu is opened. This leads to some drawing operations on
splitview implementation, even though these should be skipped.
The focusItem might even be re-positioned into incorrect position
due to the failure.
As a fix, check if the focusItem is already positioned correctly
and avoid doing anything when it already is.
Task-number: QTBUG-18738
Reviewed-by: Guoqing Zhang
|
|
|
|
|
|
|
|
|
|
|
|
| |
Avkon calls BeginFullScreen() and EndFullScreen() to trigger the
fullscreen system transition effects for application exit, however
the calls are made too late for Qt apps because the widgets are
already destroyed. Instead, the effects are triggered explicitly
from Qt, before closing the widgets, or from aboutToQuit, whichever
comes first.
Task-number: QT-4718
Reviewed-by: Jani Hautakangas
|
|
|
|
|
|
|
|
|
| |
When raster graphics system is forced and the HW was capable enough,
we still tried to use SetSurfaceTransparency() on the RWindow to
enable semi-transparency, which is wrong as it only works for
windows that have a separate surface.
Reviewed-by: Jani Hautakangas
|
|
|
|
|
|
|
|
|
| |
Splitview changes cause application to crash, since the cancellation of
FEP transaction is not notified to the native side. This leads
the native side and Qt to be not in sync.
Task-number: QT-4879
Reviewed-by: Guoqing Zhang
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The backing store tracker's registerWidget and unregisterWidget
functions are called when EPartiallyVisible and ENotVisible events
come from WSERV. However if an application sends its window group
to background right after caling show() and before entering the
event loop, there is a chance that all the application will receive
is an ENotVisible event, leading to calling unregisterWidget() without
a previous registerWidget(). In this case the backing store was
not destroyed and the application was consuming GPU memory even while
it was staying in background. This patch ensures registerWidget() is
called always before unregisterWidget() in the Symbian-specific
event handler for ENotVisible, and replaces the previous patch,
a12d41076919a133e63de63dff5c1a131a0564e4, which caused regression
in autotests.
Task-number: QTBUG-18493
Reviewed-by: Gareth Stockwell
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Applications can request the usage of RWindow::FixNativeOrientation()
by setting the new Qt::WA_SymbianNoSystemRotation attribute for their
fullscreen top-level widget (which in practice will either be a
graphics or declarative view). This will fix the underlying EGL
window surface and the QWidget dimensions to the dimension of the
native orientation of the device (typically portrait). The default
auto-rotation can be left enabled, however it will be up to the
application to rotate the drawing. Global notifications, VKB, etc.
will still appear in the proper orientation. Another benefit is
improved performance in the non-native orientation.
Task-number: QTBUG-17742
Reviewed-by: Jason Barron
Reviewed-by: Jani Hautakangas
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
QS60Style deduces incorrectly when itemview only contains checkbox.
This is minor, yet highly annoying bug that prevents highlighted
itemview item from showing its content with themes that have opaque
itemview item highlight (highlight covers the text that is underneath).
As a fix, check itemview item text and icon content before declaring
it as "checkbox only".
Task-number: QTBUG-18694
Reviewed-by: Tomi Vihria
|
|
|
|
| |
This reverts commit a12d41076919a133e63de63dff5c1a131a0564e4.
|
|\ |
|
| |
| |
| |
| |
| | |
Task-number: QTBUG-16207
Reviewed-by: Sami Merila
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
tst_QListView::taskQTBUG_2678_spacingAndWrappedText() fails because:
QS60Style adds to the itemview item content size margins and empty
space, which shouldn't be part of the content size.
As a fix, remove these.
taskQTBUG_435_deselectOnViewportClick() fails because:
Sending a click to a selected itemview item, when it should be sent
to below that specific one. It was using hardcoded (center + 20) and
autotest assumed that this would be outside of first item.
In S60 with touch support, the itemview items are rather tall
(49 pixels). As a fix, autotest now uses calculated value, which
ensures that click is sent to outside first item.
Task-number: QT-4810
Reviewed-by: Tomi Vihria
|
|
|
|
|
| |
Task-number: QTBUG-16027
Reviewed-by: Sami Merila
|
|
|
|
|
|
|
|
|
|
|
| |
In SR.11 there is a new theme graphics (with separate ID) for
TabWidget tab shapes. Also, shapes are no longer set overlapped,
but are side-by-side without any gaps.
Earlier releases still use the existing graphics with overlapping.
Task-number: QT-4762
Reviewed-by: Miikka Heikkinen
|
|\ |
|
| |
| |
| |
| |
| | |
Task-number: QTMOBILITY-1494
Reviewed-by: Gareth Stockwell
|
|/
|
|
|
|
|
|
|
|
|
|
| |
When splitview closes (i.e. keyboard is dismissed), application's
graphicsview containing the input widget (focus item) is reset back to
original graphicsview transformation.
As a fix, resetTransform is always called, when rootItem is found
from graphicsView.
Task-number: QT-4858
Reviewed-by: Guoqing Zhang
|
|
|
|
|
|
|
| |
Added include to the previous fix to prevent compilation issue.
Task-number: QT-4559
Reviewed-by: Tomi Vihria
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
QS60Style uses different theme background for dialogs. However,
labels use just one color irregardless of background texture.
Therefore, in certain themes, this might produce an issue, where
foreground color (label) is not visible from background.
To fix this, set the label color to correct theme color when
label is contained within a dialog.
Task-number: QT-4559
Reviewed-by: Tomi Vihria
|
|
|
|
| |
Reviewed-by: axis
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fullscreen with softkeys dialogs would draw twice when orientation
was changed to landscape, causing flicker. This happened because
status pane change event and layout change event both caused
redraw with different client area size. Added a check to avoid
handling client area change on account of status pane change, if status
pane is not visible and there was no change in its visibility.
Task-number: QTBUG-18496
Reviewed-by: Sami Merila
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The backing store tracker's registerWidget and unregisterWidget
functions are called when EPartiallyVisible and ENotVisible events
come from WSERV. However if an application sends its window group
to background right after caling show() and before entering the
event loop, there is a chance that all the application will receive
is an ENotVisible event, leading to calling unregisterWidget() without
a previous registerWidget(). In this case the backing store was
not destroyed and the application was consuming GPU memory even while
it was staying in background. This patch makes unregisterWidget()
not to check the widget's presence in the m_widgets set, instead
the condition for deleting the backing store is solely an empty set.
Task-number: QTBUG-18493
Reviewed-by: Gareth Stockwell
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently it is not possible to enter negative number to QSpinBox (or
to any other QWidget which is handling numeric input only) in touch
devices. This is due to that AVKON virtual keyboards have
negative sign (-) in special character table(s) and it is not
accessible by default from QWidgets, unless you define widget's input
hints as ImhFormattedNumbersOnly AND ImhDialableCharactersOnly
(or non-numeric).
With this fix, default special character table is added for widgets
with numeric input mode AND either ImhFormattedNumbersOnly or
ImhDialableCharactersOnly.
By default user is still unable to enter nagative values to QSpinBox,
but developer can set inputMethodHint to work around the issue:
widget->setInputMethodHints(Qt::ImhFormattedNumbersOnly);
Task-number: QTBUG-17461
Reviewed-by: Miikka Heikkinen
|
|
|
|
|
|
|
|
|
|
| |
The qbrush autotest was failing on Symbian, because gradient stops
with NaN position cannot be inserted on Symbian. This is caused by
the pos > 1 || pos < 0 check in setColorAt() which is incorrect
on ARM as NaN > 1 will evaluate to true.
Task-number: QTBUG-17874
Reviewed-by: Samuel Rødal
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Qt application was previously not setting a native framework's flag to
indicate that is supports "single touch" (i.e. activating an item would
only need one tap, instead of one tap to highlight and another to
activate) for Sym^3.
This was causing the native dialogs launched from within the
application to behave as Sym^1 dialogs.
As a fix, set the native flag when running Qt in Sym^3.
Task-number: QT-4569
Reviewed-by: Jani Hautakangas
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Dialog softkeys are covered by Qt Application's Softkeys
Updating softkeys while showing a native dialog, pushes Qt application CBA
on top of dialog CBA. Therefore, native dialog can not be dismissed.
As a workaround, when gaining focus to a window, do not update application
softkeys, if there is a native dialog shown.
Task-number: QTBUG-18486
Reviewed-by: mread
|
|
|
|
|
|
|
|
|
|
| |
Fullscreen child windows of non-fullscreen main application window
displayed softkeys and status bar when they shouldn't. Fixed it so that
fullscreen windows never display these items (except for softkeys when
explicitly specified to do so.)
Task-number: QTTH-1207
Reviewed-by: Sami Merila
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Calling QSymbianControl::setFocusSafely(true) on currently focused
window causes the next window in stack to get the focus momentarily,
leading to various softkey problems, such as leaving child window's
softkeys around when child is closed and flickering softkeys when child
is opened. Added a check to QWidget::activateWindow to avoid calling
setFocusSafely for already focused windows.
Task-number: QTBUG-18409
Reviewed-by: Sami Merila
Reviewed-by: axis
|
|
|
|
|
|
|
|
|
| |
Fix for QTBUG-16858 improved somewhat QComboBox menu drawing, but
unfortunately caused regression in QMenu and dialog background
drawing. These widgets shouldn't reserve space for PM_MenuVMargin.
Task-number: QTBUG-18482
Reviewed-by: Dmitry Trofimov
|
|
|
|
|
|
|
|
|
| |
Additional fix for this task. Make the separator slightly less wide,
since on some themes the menu background border might be transparent
near the left and right borders.
Task-number: QTBUG-10054
Reviewed-by: Tomi Vihria
|
|
|
|
|
|
|
|
| |
QSoftKeyManager maps the StandardSoftKey values to Symbian commands.
This way the softkeys are using Symbian defined icons.
Task-number: QT-4620
Reviewed-by: Sami Merila
|
|\
| |
| |
| | |
merge-requests/2584
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In Symbian^3 clearing softkeys with -1 value resulted useless Exit
button. EAknSoftkeyEmpty is used instead to remove the extra button.
There is no flickering with softkeys when using EAknSoftkeyEmtpy with
Symbian^3.
Task-number: QT-4557
Reviewed-by: Sami Merila
|
| |\
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
4.7-integration
* '4.7' of scm.dev.nokia.troll.no:qt/qt-doc-staging: (185 commits)
qdoc: Avoid infinite loops in table of contents generation.
Removed the documentation from the install rule.
qdoc: Added the <othermeta> element.
qdoc: Completed changing <section> structure.
Doc: Fixed reference to absolete API in exceptionsafety.html
Doc: Removed links to obsolete API in QResource
Doc: Fixed broken links in QIcon::fromTheme()
Doc: Fixed doc bug in undo framework example
Doc: Fixed typo.
qdoc: Changed <section> structure.
Doc: Typo fixes
Doc: Fixed snippet documenting QMetaObject::classInfo
Doc: Cannot alter SelectionMode of a combobox's view
qdoc: Added <publisher> and <permissions> elements.
qdoc: Added <component> element to contain the module name.
qdoc: Added <prodinfo> element and its contents to the metadata.
Doc: Fixed a doc bug in the Rogue example
Doc: Small change to QByteArray::resize()
Doc: Small change to ListModel docs
Doc: QtDemo now gives error message when example doc cannot be loaded
...
|
| | |\
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
doc/src/declarative/declarativeui.qdoc
doc/src/examples/qml-examples.qdoc
|
| | |\ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Task-number: QTBUG-14445
Reviewed-by: Jerome Pasion
|
| | | | |
| | | | |
| | | | |
| | | | | |
Task-number: QTBUG-9990
|
| | | | |
| | | | |
| | | | |
| | | | | |
Reviewed-by: David Boddie
|
| | | | | |
|
| | |\ \ \
| | | |/ /
| | |/| |
| | | | |
| | | | |
| | | | | |
Conflicts:
doc/src/declarative/dynamicobjects.qdoc
doc/src/declarative/elements.qdoc
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Task-number: QTBUG-17858
Reviewed-by: axis
|
| | |\ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
merge-requests/1113
Conflicts:
doc/src/development/qmake-manual.qdoc
|
| | |\ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
merge-requests/1108
Conflicts:
doc/src/declarative/basictypes.qdoc
|
| | |\ \ \ \ \ |
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Task-number: QTBUG-16900
|
| | | | | | | | |
|
| | |\ \ \ \ \ \
| | | |/ / / / /
| | |/| | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Conflicts:
doc/src/declarative/qdeclarativemodels.qdoc
doc/src/index.qdoc
doc/src/template/style/style.css
tools/qdoc3/atom.h
tools/qdoc3/doc.cpp
tools/qdoc3/doc/qdoc-manual.qdoc
tools/qdoc3/doc/qdoc-manual.qdocconf
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
11 instances of raw-html remain.
|