| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
| |
When the pro file is processed with qmake and it EPOCROOT is not set
then it will give out warnings. This is really only an issue when
configure on X11 is ran because this runs qmake on all pro files
anyway.
So rather than confusing users about what this warning message means on
a non Symbian platform, we just ensure that the pro file specifically
only does anything useful on Symbian platforms.
Reviewed-by: Gareth Stockwell
|
|\
| |
| |
| |
| |
| |
| | |
4.6-integration
* '4.6' of scm.dev.nokia.troll.no:qt/oslo-staging-2:
Bump version number after 4.6.3 release.
|
| |
| |
| |
| | |
Reviewed-by: Trust Me
|
| |
| |
| |
| | |
This bug was introduced with bug fix 558089fb21e7f388f9810c51abbd9bf3872b2178
|
| |
| |
| |
| |
| | |
Task-number:QTBUG-2414
Reviewed-by:Dmytro Poplavskiy
|
|/
|
|
|
|
|
|
| |
Changed gif default frame rate from 0 to 100ms.
This is the same as what web browsers seem to be using.
Task-number:QTBUG-2441
Reviewed-by:Dmytro Poplavskiy
|
|
|
|
|
|
|
|
|
|
| |
The PowerVR screen driver was using QTransformedScreen::tranformation()
which is in a class that is Q_AUTOTEST_EXPORT. That means that it would
only work with a developer build. This contributed patch changes it to
QScreen::transformOrientation() instead which is Q_GUI_EXPORT.
Task-number: QTBUG-10193
Reviewed-by: Lorn Potter
|
|
|
|
|
|
|
|
| |
This fixes a problem with accessibility and QFileDialog, in addition the
fix to complexwidgets.cpp will also fix any itemview that uses a root
index.
Reviewed-by: Jan-Arve
|
|
|
|
|
|
|
| |
Clean up the function a little and make sure I don't call
QImage::hasAlphaChannel twice for opaque images.
Reviewed-by: muthu <qt-info@nokia.com>
|
|
|
|
|
|
|
| |
We don't need to do the conversion using QImage when NoOpaqueDetection
is specified.
Reviewed-by: muthu <qt-info@nokia.com>
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Symbian^3 introduces a new compositing graphics subsystem in which
non-UI content such as video is provided by client applications via
graphics surfaces.
This patch modifies the video playback part of the Phonon MMF backend
so that, on devices which use the new graphics architecture (NGA),
video is rendered to a surface. On devices which use the legacy
graphics architecture, the existing video rendering path, which uses
Direct Screen Access (DSA) is maintained.
On NGA devices, video playback applications do not deal with surfaces
directly; instead, they use a new MMF client API called
CVideoPlayerUtility2. The implementation of this API takes care of
creating a graphics surface, registering it with the window manager,
and directing the output of the video decoder into this surface.
CVideoPlayerUtility2 inherits from the legacy video playback API,
CVideoPlayerUtility, deprecating certain functions and adding new ones.
The main changes involved in modifying CVideoPlayerUtility client code
to instead use CVideoPlayerUtility2 are:
1. CVideoPlayerUtility requires a window handle to be provided at
object construction time.
The CVideoPlayerUtility2 constructor does not take a window
handle; it is provided by the client later via the
SetDisplayWindowL function.
2. CVideoPlayerUtility requires the client to provide an absolute
screen rectangle at construction time, and then to call
SetDisplayWindowL whenever this rectangle changes due to either
window repositioning or resizing.
CVideoPlayerUtility2 requires the client to provide a display
rectangle which is relative to the display window. This
rectangle must be updated via SetVideoExtentL /
SetWindowClipRectL when the window is resized, but no update is
required when the window is repositioned - the compositing
window system takes care of repositioning the video content on
the screen.
3. CVideoPlayerUtility requires the client to paint transparent
black into the region of the window in which video will be
displayed. CVideoPlayerUtility2 does not require the client
to paint the video window.
In order to accomodate these differences, the existing VideoPlayer and
VideoOutput classes are replaced with AbstractVideoPlayer and
AbstractVideoOutput respectively. These abstract base classes
encapsulate functionality which is common between the DSA and surface
rendering client code. Because CVideoPlayerUtility2 inherits from
CVideoPlayerUtility, AbstractVideoPlayer is able to hold a pointer to
CVideoPlayerUtility, via which it controls functionality which is not
affected by the details of the rendering path, such as play/pause/stop,
seek and metadata access.
The three areas of divergence listed above are encapsulated in the
derived classes DsaVideoOutput/SurfaceVideoOutput and DsaVideoPlayer/
SurfaceVideoPlayer. Of the three, (1) and (3) are fairly
straightforward. For DSA video playback, the need to respond to
changes in video widget absolute screen position in (2) necessitated
the AncestorMoveMonitor class, which installs an event filter on each
ancestor of the video widget. This class is not required for surface
video playback and is therefore removed from the surface-rendering
code path.
Selection of either the DSA- or surface-rendering code path is done
at qmake time, via the exists(...) check introduced in mmf.pro. This
checks for existence of the header in which CVideoPlayerUtility2 is
defined; if this file is found, surface rendering is selected,
otherwise the DSA rendering version of the backend is built. Note that
this approach is not completely robust, since it is possible for an
environment to include the videoplayer2.h header and yet be configured
to use the legacy graphics subsystem. This could be dealt with by
instead performing the check for surface support at configuration time,
building and executing a small Symbian program which will return
different output according to which of the two graphics subsystems is
in use.
Task-number: QTBUG-8919
Reviewed-by: Frans Englich
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Configure parameter -qtlibinfix will now change also plugin names
of plugins built and installed with Qt in Symbian.
Default plugin path is changed to: /resource/qt<libinfix>/plugins.
Other plugins besides the ones installed with Qt are not renamed.
With infixed configuration, Qt can be installed on a phone that already
has a Qt installed on ROM without interfering with the ROM version of
Qt.
Note that since s60main.rsc resource cannot deployed with infixed Qt,
and infixing it is somewhat problematic, currently the phone needs
to have proper Qt installation, too, for infixed Qt to work.
It also means that any changes to Qt that would affect s60main.rsc
cannot be tested on real device using infixed builds. Since this file
is unlikely to need changing, this should not be a big problem.
Task-number: QTBUG-9065
Reviewed-by: Jani Hautakangas
|
|
|
|
|
|
|
|
|
| |
Changed backend from being a plugin, to being statically compiled into
QtMultimedia.dll. This is to achieve consistency with the backends for
other plugins, and to allow the plugin API to be modified.
Task-number: QTBUG-8994
Reviewed-by: trustme
|
|
|
|
|
|
|
| |
Part of QtP delta reduction effort.
Task-number: QT-3055
Reviewed-by: Janne Koskinen
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| | |
4.6-integration
* '4.6' of scm.dev.nokia.troll.no:qt/oslo-staging-1:
Updated WebKit from /home/shausman/src/webkit/trunk to qtwebkit/qtwebkit-4.6 ( 266a6c4f1938dd9edf4a8125faf91c62495e3ce2 )
Doc: Removed lie that access to QBuffer is unbuffered.
Minisplitter doesn't paint to the bottom/right
Avoid unnecessary memory allocation in the jpeg handler's image detection
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The handler calls peek with 2 bytes to inspect the first two bytes. Instead
of calling the overload of peek() that returns a new QByteArray with just
two bytes, allocate 2 bytes on the stack and call the overload of peek()
that writes into the specified buffer.
Reviewed-by: Joao
|
|\ \
| |/
|/|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
4.6-integration
* '4.6' of scm.dev.nokia.troll.no:qt/qt-s60-public:
Fixed dialog resize not to move the dialog for Symbian.
Fix SDP files are not supported.
Fix build break caused by undefined symbol SetDialogPreference
Renamed test benchmark targets.
Added check for null pointer in qt_vg_unregister_pixmap.
Add '.' dir as the first include directory in Symbian
Enabled some examples by default in Symbian builds
Added forwarding headers for qplatformdefs.h in Symbian mkspecs
QUnixPrintWidget should not be declared in Symbian
Fix sqlite3_v9.2.zip to export sqlite3.iby to correct location.
Export qtdemoapps.iby to proper location
Added some missing IBY export paths to platform_path.prf
|
| |\
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
4.6-integration
* '4.6' of scm.dev.nokia.troll.no:qt/qt-s60-public:
Fixed dialog resize not to move the dialog for Symbian.
Fix SDP files are not supported.
Fix build break caused by undefined symbol SetDialogPreference
Renamed test benchmark targets.
Added check for null pointer in qt_vg_unregister_pixmap.
Add '.' dir as the first include directory in Symbian
Enabled some examples by default in Symbian builds
Added forwarding headers for qplatformdefs.h in Symbian mkspecs
QUnixPrintWidget should not be declared in Symbian
Fix sqlite3_v9.2.zip to export sqlite3.iby to correct location.
Export qtdemoapps.iby to proper location
Added some missing IBY export paths to platform_path.prf
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
sqlite3.iby needs to be exported under epoc32/rom/include/core/mw,
instead of epoc32/rom/include.
Part of QtP delta reduction effort
Reviewed-by: TrustMe
|
|/ /
| |
| |
| |
| | |
Task-number: Related to QTBUG-5117
Reviewed-by: Jørgen Lind
|
|/
|
|
|
|
| |
Don't use localtime_s.
Reviewed-by: thartman
|
|
|
|
|
|
| |
QList<T>::remove() is QT3_SUPPORT, replace with erase().
Reviewed-by: Jervey Kong <jervey.kong@nokia.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since DirectFB always uses the front buffer of a double buffered surface
as the source when blitting we needed to make sure that the front buffer
was valid and hence we called Flip for each scroll. This had negative
performance impacts since you could end up with various parts of a
window being updated at different times.
With this patch we store whether the front-buffer is up to date inside
the window surface and only call Flip in scroll if it's not.
Reviewed-by: Jervey Kong <jervey.kong@nokia.com>
|
|
|
|
|
|
|
| |
DirectFB will print a warning for this since the file doesn't exist but
we might as well not try when we know the file doesn't exist.
Reviewed-by: Donald Carr <donald.carr@nokia.com>
|
|
|
|
|
|
| |
DSPF_DST was added in 1.2.9, not in 1.2.0
Reviewed-by: muthu <qt-info@nokia.com>
|
|
|
|
|
|
|
| |
If you call fillRect(QBrush(QColor())); we should short-circuit before
falling back to the raster engine.
Reviewed-by: muthu <qt-info@nokia.com>
|
|
|
|
|
|
|
|
| |
If you specify an operation that is not recognized in
QT_DIRECTFB_WARN_ON_RASTERFALLBACKS or
QT_DIRECTFB_DISABLE_RASTERFALLBACKS
Reviewed-by: muthu <qt-info@nokia.com>
|
|
|
|
|
| |
Task-number: QT-1849
Reviewed-by: Jeremy
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Allow people to control whether or not to warn on/disable raster
fallbacks using the following mechanism:
export QT_DIRECTFB_DISABLE_RASTERFALLBACKS="draw_pixmap|draw_text"
export QT_DIRECTFB_WARN_ON_RASTERFALLBACKS="draw_lines"
It's still possible to define QT_DIRECTFB_WARN_ON_RASTERFALLBACKS to
something for legacy reasons.
The environment variable check is only available in debug mode.
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
It seems that I have to premultiply the colors I pass to
IDirectFBSurface->SetColor when composition mode != Source|SourceIn.
It now seems to behave the same way as the raster engine which I guess
should be considered the authority on this matter.
Reviewed-by: Noam Rosenthal <noam.rosenthal@nokia.com>
|
| |
| |
| |
| |
| |
| |
| |
| | |
Qt heuristics say that a QPixmap becomes an alpha pixmap when filled
with a color with alpha != 255 but not that it returns to being opaque
when filled with a color with alpha == 255
Reviewed-by: Noam Rosenthal <noam.rosenthal@nokia.com>
|
| |
| |
| |
| |
| |
| | |
This porter duff rule was added in DirectFB 1.2
Reviewed-by: Noam Rosenthal <noam.rosenthal@nokia.com>
|
|/
|
|
|
|
|
|
| |
Fixed ODBC to use SQLTCHAR type and not assume that wchar's are 2
bytes wide.
Task-number: QTBUG-6928
Reviewed-by: Justin McPherson
|
|
|
|
|
|
| |
If DirectFB fails to lock a surface it won't necessarily set mem to 0.
Reviewed-by: Jervey Kong <jervey.kong@nokia.com>
|
|
|
|
|
|
|
|
| |
If you're only updating parts of a widget we have to make sure
DSFLIP_BLIT is included. Otherwise Qt's assumptions about the backing
store breaks.
Reviewed-by: Jervey Kong <jervey.kong@nokia.com>
|
|
|
|
|
|
|
|
|
|
| |
Certain boards do not properly support IDirectFBSurface->Flip() with a
partial DFBRegion passed in.
This problem can be worked around by exporting:
QWS_DISPLAY=directfb:nopartialflip
Reviewed-by: Jervey Kong <jervey.kong@nokia.com>
|
|
|
|
|
|
|
| |
This was already possible in non-WM mode. I now enable using the
same connect argument to make it work for WM.
Reviewed-by: Jervey Kong <jervey.kong@nokia.com>
|
|
|
|
|
|
|
|
|
| |
Since we don't have a dedicated function that gets called when isOpaque
changes for a window we do not support making an existing window
non-opaque at runtime. Supporting this would require considerable
overhead per flush and we do not want that.
Reviewed-by: Jervey Kong <jervey.kong@nokia.com>
|
|
|
|
|
|
| |
The logic was reversed.
Reviewed-by: Jervey Kong <jervey.kong@nokia.com>
|
|
|
|
| |
Forgot to fill in the module name in 4cabe964.
|
|
|
|
| |
Fixes incorrect license headers used on files added by 28610950.
|
|
|
|
| |
Task-number: QT-567
|
| |
|
|
|
|
|
|
|
| |
This function is only exported when DirectFB is built as part of
libQtGui.
Reviewed-by: Jervey Kong <jervey.kong@nokia.com>
|
|
|
|
|
| |
Task-number: QTBUG-7037
Reviewed-by: Kim
|
|
|
|
|
|
|
|
| |
When creating the driver instance two parameters are given to the
driver. But it accepts only the name of the device to be used.
Reviewed-by: Paul
Merge-request: 2288
|
|
|
|
|
|
|
| |
Rework the previous commit a bit and include caching of image sizes.
Task-number: QTBUG-6696
Reviewed-by: Kim
|