| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Use ExpandToTransparentBorderPadMode since we can use GL_CLAMP_TO_EDGE
to clamp to the texture.
* Shrink the bounding rects reported by the blur
and drop shadow filters (expanding by 2 * radius isn't needed).
* Use a single-pass blur for radii <= 3 to avoid the overhead of
rendering to an FBO.
* Made the fast blur setting generate filters for only a predefined set
of radii, and then use the actual blur radius to spread the sample
points outwards.
* Optimized the generated program to rely less on temporary variables,
as those seemed to not be handled very well by certain GLSL compilers.
Reviewed-by: Gunnar Sletta
|
| |
|
|
|
|
|
| |
There's no reason to lock ourselves to int in the API when some of the
backend could handle floating point blur radii.
Reviewed-by: Bjørn Erik Nilsen
|
| |
|
|
|
|
| |
Usable for future optimizations.
Reviewed-by: Samuel
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| | |
When blurring and the blur radius increases we need a bigger effect rect
to do within-pixmap-bounds filtering.
Reviewed-by: Bjørn Erik Nilsen
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is new API and we don't want to add several items that are not
strictly needed. This is a new set of features and we can grow them
once we have more input from users on what is needed.
The Bloom filter was added based on input from designers, but is not
implemented according to how designers think of blook, so the effect
doesn't meet the requirements.
The Grayscale filter is functionally a duplicate of the colorize
filter and is therefore not needed.
The Pixelize filter has no genuine usecase.
Reviewed-by: Samuel
|
| |
|
|
|
|
|
| |
If an effect is applied repeatedly on the same source, just with
varying parameters, we can save a lot by caching the source pixmaps.
Reviewed-by: Bjørn Erik Nilsen
|
| |
|
|
|
|
| |
There's no implicit conversion from QPixmap to QImage
Reviewed-by: Gunnar
|
| |
|
|
|
|
|
| |
Avoid doing so many conversions by operating on raster pixmaps, and by
using INV_PREMUL/PREMUL instead of converting to ARGB32.
Reviewed-by: Gunnar Sletta
|
| |
|
|
|
|
|
|
|
|
|
| |
The blur, drop shadow, and bloom graphics effects are scale dependent,
since they have radius and offset (in the case of drop shadow)
parameters that are specified in device coordinates. Thus, we can't
apply the effect in logical coordinates and scale up, and need to always
use the device coordinate path for these effects. The opacity and
grayscale effects still use the logical coordinate optimization.
Reviewed-by: Gunnar Sletta
|
| |
|
|
|
| |
Merge-request: 1716
Reviewed-by: Thiago Macieira <thiago.macieira@nokia.com>
|
| | |
|
| |
|
|
|
|
|
| |
This allows the user to control whether to use a fast dynamic blur or
a static high quality blur.
Reviewed-by: Samuel
|
| |
|
|
|
|
|
|
|
|
|
| |
We need a way to control various rendering operations. For example,
whether quality is more important than performance, or the other way
around.
This change also replaces occurences of QPixmapFilter/QGraphicsEffect::BlurHint
(introduced in 1a431e850893b6b162c833f4f148f090e2427dda) with Qt::RenderHint.
Reviewed-by: Samuel
|
| |
|
|
|
|
|
|
| |
This effect was removed in 1c9a28ea64cc53e61a64644dc5a4ff121b475bc5, but
has now been readded on request from a couple of customers. Andreas also
agreed we should provide this effect.
Reviewed-by: Andreas
|
| |
|
|
|
|
|
|
| |
This lets the user control whether to use a fast dynamic blur when
animating the radius of the blur for example, or to use a static high
quality blur for one-time or constant radius blurring.
Reviewed-by: Gunnar Sletta
|
| |
|
|
|
|
|
| |
This greatly increases the blur quality in the OpenGL implementation,
and doesn't affect the performance of the raster implementation.
Reviewed-by: Bjørn Erik Nilsen
|
| | |
|
| |
|
|
|
| |
Autotest: included
Reviewed-by: Bjørn Erik Nilsen
|
| |
|
|
| |
Reviewed-by: Trust Me
|
| |
|
|
|
|
|
| |
The custom shader code in the OpenGL2 paint engine needs time to
mature before we make this official public API.
Reviewed-by: trustme
|
| |
|
|
| |
That's the last of them... for now.
|
| |
|
|
| |
The pixmap was painted at wrong offset.
|
| |
|
|
|
|
|
|
|
| |
In the case of applying an effect to a QGraphicsItem, we have to notify
the scene's BSP that the item's bounding rect has changed. We do this
by calling prepareGeometryChange().
In the case of QWidget, it's sub-optimal that we update its parent, but
there's no other way to solve it at the moment.
|
| |
|
|
| |
Reviewed-by: Andreas
|
| |
|
|
| |
Reviewed-by: Leo
|
| |
|
|
| |
Reviewed-by: Trust Me
|
| |
|
|
|
| |
We only have to do it when the opacity changes (in ::setOpacity).
Also, we cannot do the cut-off when the effect has an opacity mask set.
|
| |
|
|
|
|
|
|
| |
Opacity masks enable you to make portions of an element transparent.
More information about opacity masks here:
http://msdn.microsoft.com/en-us/library/ms743320.aspx
Reviewed-by: Samuel
|
| | |
|
| | |
|
| |
|
|
| |
Reviewed-by: Kavindra
|
| |
|
|
|
|
| |
classes
Reviewed-By: TrustMe
|
| |
|
|
| |
Reviewed-By: TrustMe
|
| |
|
|
| |
Reviewed-By: TrustMe
|
| |
|
|
| |
QPoint -> QPointF
|
| | |
|
| | |
|
| |
|
|
| |
Reviewed-by: Trust Me
|
| |
|
|
|
|
| |
This is a common effect that many many customers have asked for.
Reviewed-by: Samuel
|
| | |
|
| | |
|
| |
|
|
| |
Discussed with Andreas.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
QGraphicsEffect is no longer dependent on the Graphics View module.
|
| | |
|
| |
|
|
| |
These belong to the examples directory as discussed with Andreas.
|
| |
|
