| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
Don't invalidate the cache if we're only translating and the effect rect
is fully contained within the device rect of the painter.
Task-number: QTBUG-6901
Reviewed-by: Bjørn Erik Nilsen
|
|
|
|
| |
Reviewed-by: Trust Me
|
|
|
|
|
|
|
|
| |
This lets us ignore the invalidateCache call when the transform of a
graphics item with an effect changes, and the cached system is
LogicalCoordinates and cached mode is not PadToEffectiveBoundingRect.
Reviewed-by: Bjørn Erik Nilsen
|
|
|
|
|
|
|
| |
Q3MainWindow and Q3TitleBar depend on it.
Reviewed-By: dt
Reviewed-By: Alessandro Portale
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Get rid of QGraphicsEffectSource from the public API, instead add
convenience functions in QGraphicsEffect. This way we commit to less
API, and are free to introduce a customizable QGraphicsEffectSource
in a future release.
* Move PixmapPadMode into QGraphicsEffect and tweak the names of the
enum values.
* Make QGraphicsBlurEffect::BlurHint into a bit flag, for extensibility.
Reviewed-by: Bjørn Erik Nilsen
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
It depends on QT_NO_GRAPHICSVIEW for now, but it is possible to remove
this dependency.
Reviewed-by: paul
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Building QtSvg for Symbian (ARMV5 build) fails due to the following linker
error:
QGraphicsEffectSourcePrivate::invalidateCache(bool) const
(referred from qsvgwidget.o). This function is called from the
inline destructor of QGraphicsEffectSourcePrivate. Making this
destructor non-inline fixes the problem.
It is not clear why QtSvg is instantiating this destructor, however, as
neither QGraphicsEffectSourcePrivate nor any of its derived classes are
referred to from QtSvg source.
This problem seems to have been triggered by 85e41590.
Reviewed-by: Shane Kearns
|
|
|
|
|
|
|
| |
When the effect rect changes we only need to invalidate the cache if the
mode is ExpandToEffectRectPadMode.
Reviewed-by: Gunnar Sletta
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* 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
|
|
|
|
|
|
| |
Usable for future optimizations.
Reviewed-by: Samuel
|
|\ |
|
| |
| |
| |
| | |
Reviewed-by: Samuel
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
Reviewed-by: thartman
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
Autotest: included
Reviewed-by: Bjørn Erik Nilsen
|
|
|
|
| |
Reviewed-by: Trust Me
|
|
|
|
|
|
|
|
|
| |
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: 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
|
|
|
|
|
|
|
| |
Lots of warnings in the qreal == float case.
Some Q_UNUSED added.
Reviewed-by: thartman
|
|
|
|
| |
Reviewed-by: Trust Me
|
|
|
|
|
|
| |
This is a common effect that many many customers have asked for.
Reviewed-by: Samuel
|
| |
|
| |
|
|
|
|
| |
Discussed with Andreas.
|
|
|
|
| |
Graphics effects is no longer dependent of graphics view.
|
|
|
|
| |
These belong to the examples directory as discussed with Andreas.
|
|
|