Qt.git - Qt s a cross-platform application framework that is used for developing application software that can be run on various software and hardware platforms with little or no change in the underlying codebase, while still being a native application with native capabilities and speed.

	Commit message (Collapse)	Author	Age	Files	Lines
*	Merge remote branch 'origin/4.6' into qt-4.7-from-4.6	Rohan McGovern	2010-03-06	1	-1/+1
\|\ \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Conflicts: configure.exe examples/multimedia/audioinput/audioinput.cpp src/corelib/io/qfsfileengine.cpp src/gui/egl/qegl_wince.cpp src/gui/egl/qeglproperties.cpp src/gui/egl/qeglproperties_p.h src/gui/embedded/directfb.pri src/gui/kernel/qapplication_win.cpp src/gui/painting/qdrawutil.cpp src/opengl/qgl_p.h src/sql/drivers/odbc/qsql_odbc.cpp src/sql/drivers/odbc/qsql_odbc.h tests/auto/auto.pro tests/auto/qgl/tst_qgl.cpp translations/assistant_adp_ru.ts
\| *	Uncomment #DIRECTFB_DRAWINGOPERATIONS in pri-file	Anders Bakken	2010-03-01	1	-1/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	This has no effect unless QT_DIRECTFB_WARN_ON_RASTERFALLBACKS or QT_DIRECTFB_DISABLE_RASTERFALLBACKS is defined but will decrease likelyhood of customers encountering strange compile errors if they don't uncomment it when using these defines. Reviewed-by: Noam Rosenthal <noam.rosenthal@nokia.com>
* \|	Lock before calling drawStaticTextItem	Anders Bakken	2010-02-02	1	-1/+1
\|/ \| \| \|	Reviewed-by: Donald Carr <donald.carr@nokia.com>
*	Make stretchblit an opt-out option in DirectFB	Anders Bakken	2010-01-04	1	-0/+1
\| \| \| \| \| \| \| \|	Certain boards are not support StretchBlit very well. This patch enables them to define QT_NO_DIRECTFB_STRETCHBLIT to fall back to the raster engine for stretchblits. Reviewed-by: Donald Carr <donald.carr@nokia.com>
*	Make QT_DIRECTFB_SUBSURFACE an opt-in option	Anders Bakken	2009-10-15	1	-1/+1
\| \| \| \| \| \| \| \| \|	Previously you had to define QT_NO_DIRECTFB_SUBSURFACE to prevent Qt from using subsurfaces for locked surfaces. Now make the default be QT_NO_DIRECTFB_SUBSURFACE and rather allow people to define QT_DIRECTFB_SUBSURFACE to use this option. Reviewed-by: Donald Carr <donald.carr@nokia.com>
*	Implement QDirectFBPaintEngine::drawRoundedRect	Anders Bakken	2009-09-18	1	-1/+1
\| \| \| \| \| \|	We need to lock before falling back to QRasterPaintEngine Reviewed-by: Jervey Kong <jervey.kong@nokia.com>
*	Make QT_DIRECTFB_PALETTE an opt-in option	Anders Bakken	2009-09-16	1	-1/+1
\| \| \| \| \| \| \|	This seems not work correctly on quite a few boards so I'd rather have people turn it on explicitly. Reviewed-by: Noam Rosenthal <noam.rosenthal@nokia.com>
*	Rewrite of DirectFB locking mechanism	Anders Bakken	2009-09-01	1	-0/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	DirectFB allows you to have a locked subSurface that remains valid while you paint on the unlocked "parent" surface. The only limitation is that when accessing the locked memory you might have to call DirectFB->WaitIdle() in case pending GPU operations aren't finished. After this we keep the locked surface around at all times (from the first time it's requested) until the surface dies. Previous calls to lock() will just call WaitIdle if necessary and previous calls to unlock now just mark the surface as dirty and in need of a WaitIdle if someone needs to access its pixel data. Reviewed-by: Donald Carr <donald.carr@nokia.com>
*	Copy directfb.pro to src/gui/embedded/directfb.pri	Anders Bakken	2009-09-01	1	-0/+38
	Reviewed-by: Thiago Macieira <thiago.macieira@nokia.com>