| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
When a painter is open on a pixmap's underlying QVolatileImage, it is
better to upload the VGImage content every time the pixmap is drawn
on the screen, in order to enable showing animations that are created
by continously rendering into the same pixmap and keeping the same
painter open.
Task-number: QT-4002
Reviewed-by: Jason Barron
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The OpenVG engine correctly uses vgClear() to fill the surface with
transparent pixels whenever the window has the WA_TranslucentBackground
attribute enabled. However both scissoring and masking affects
the operation of vgClear(). Drawing artifacts were previously
visible due this, simply because scissoring was left enabled by
the VG paint engine, and the filling with transparent pixels
happens in the window surface's beginPaint() that is called
between the paint engine's end() (for the previous paint) and
begin() (for the next paint).
Task-number: QT-4907
Reviewed-by: Jani Hautakangas
|
|
|
|
|
|
|
|
|
|
| |
Unlike OpenGL, the EGL_SWAP_BEHAVIOR_PRESERVED_BIT was not set for
the EGL configuration used with OpenVG. Yet the preserved swap was
enabled still, which, according to the EGL spec, should fail. To
make sure it still works with other EGL implementations, the bit
is now set in the configuration.
Reviewed-by: Jani Hautakangas
|
|
|
|
|
|
|
| |
Input context should prefer focus proxy over regular focus widget.
Task-number: QTBUG-18873
Reviewed-by: Miikka Heikkinen
|
|
|
|
|
|
|
|
|
| |
OpenGL context needs to be recreated on Symbian
when orientation changes. Previously only the EGL
surface was recreated which wasn't enough.
Task-number: QTBUG-18850
Reviewed-by: Samuel Rødal
|
|
|
|
|
| |
Task-number: QTBUG-17357
Reviewed-by: Jason Barron
|
|
|
|
|
|
|
|
|
| |
Cache limit can be changed to 10MB since QPixmaps
on Symbian are not consuming process heap anymore.
QPixmaps are reserved from FBServ heap.
Task-number: QTBUG-18568
Reviewed-by: Laszlo Agocs
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Recent changes in QS60Style (to support placeholder background texture)
causes the simulated style not to build. The implementation
for new method placeHolderTexture() is on the Symbian-specific
sourcefile, which is omitted in the simulator builds.
As a fix, move the implementation to the "generic" style source
file qs60style.cpp, since the method does not contain any
Symbian specific code.
Task-number: QTBUG-18863
Reviewed-by: owolff
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Timers on Symbian were always firing at least 2ms late. This was partly
due to a paranoid extra delay in Qt and the kernel being very cautious.
For one shot timers this is not so bad although a bit too much. But for
repeating timers, this can cause significant reductions in firing rate
particularly for short period timers.
The timer active object now corrects timer lateness by up to 4ms per
event. This is enough to compensate for the kernel lateness without
the possibility of wild corrections.
Task-number: QTBUG-18549
Reviewed-by: iain
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Add new enums for future Symbian platforms and fix the docs of
existing ones.
Task-number: QT-4593
Reviewed-by: Sami Merila
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
| |
Qt uses number mode keymap as a default in input context.
If Special Character Table is not assigned into FEP state,
the default keymap will be used. This will contain only few
symbols ('*', '#', ...).
As a fix, use alpha numeric keymap as a default keymap,
using this will keep the symbol table same irregardless of current
input mode (numbers, characters).
Task-number: QT-4878
Reviewed-by: Miikka Heikkinen
|
|
|
|
|
| |
Task-number: QT-4718
Reviewed-by: TRUSTME
|
|
|
|
|
|
|
|
|
|
| |
When the hardware is capable enough, setting WA_TranslucentBackground
will not lead to falling back to raster, but will continue using
OpenVG or OpenGL based rendering. However this needs an alpha channel
which was not requested previously. This patch corrects it.
Task-number: QT-4729
Reviewed-by: Jani Hautakangas
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
| |
OpenVG paint engine tries to use vgWritePixels shortcut
whenever possible to optimize rendering performance. The
check 'canVgWritePixels' failed to map formats correctly
and resulted to incorrect return value.
Task-number: QTBUG-18682
Reviewed-by: Jason Barron
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
| |
The autotest assumes that created QPixmap are exactly same irregardless
how the pixmaps were created. However, there is no guarantee that
pixmaps that look the same (i.e. in this case green rectangles)
are "same". QPixmap is platform dependent and might have e.g.
optimized format in some of the platforms.
Task-number: QT-4805
Reviewed-by: Jani Hautakangas
|
|
|
|
|
| |
Task-number: QTBUG-18647
Reviewed-by: axis
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
Task-number: QTBUG-18484
Task-number: WEBKIT-57841
Reviewed-by: axis
Reviewed-by: Janne Koskinen
|
|
|
|
| |
Reviewed-by: axis
|
|
|
|
| |
Reviewed-by: axis
|
|
|
|
| |
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
|
|
|
|
|
| |
Task-number:
Reviewed-by: Miikka Heikkinen
|
|
|
|
|
|
|
|
|
|
|
|
| |
- qaudio.dll is no longer built separately, it is static part of
QtMultimedia.dll
- s60main resources are no longer needed or generated
- Webkit files are installed via separate IBY
Task-number: QT-4839
Reviewed-by: Guoqing Zhang
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
If the path to translation file is already absolute, do not add
the $$_PRO_FILE_PWD_ to it in symbian.conf
Task-number: QT-4842
Reviewed-by: axis
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|