| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
This time with a recursive approach of processing dirty items. I've kept
the previous approach using a dirty list, but the recursive one is now
the default. Use QT_GV_USE_DIRTY_LIST=1 to swap.
I've also cached the item's device transform in both cases so that we
can re-use it later when drawing the item.
|
|
|
|
|
|
|
|
|
|
|
| |
This flag helps optimize the case where an item is used only as a
transformation node in a scene graph, and where the item itself
doesn't paint anything. This is the default for FxItem (the
subclasses that do paint enable the HasContents flag). This lets
Graphics View know whether there's any point in setting up the
world transform, opacity and other things.
Reviewed-by: Lars
|
|
|
|
| |
Regression introduced during refactoring earlier today.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Greatly simplify how we handle opacity and store it as a member in
QGraphicsItemPrivate. Remove the caching of effectiveOpacity. It's
faster to calculate it on the fly, and the recursive painting algorithm
will make even that need go away.
Reviewed-by: Andreas
|
|
|
|
|
|
|
|
| |
Since the transform is now a pointer in QGraphicsItemPrivate, we can
use this pointer directly and there's no need for a separate bitflag
anymore.
Reviewed-by: Andreas
|
|
|
|
|
|
|
|
|
| |
Now that we have a recursive painting algorithm these types of
optimizations are no longer necessary. In fact they only cause more
problems and clutter up the code unnecessarily. Removing this also
removes extra overhead from moving and transforming items.
Reviewed-by: Lars
|
|
|
|
|
|
|
|
|
|
|
| |
This flag helps optimize the case where an item is used only as a
transformation node in a scene graph, and where the item itself
doesn't paint anything. This is the default for FxItem (the
subclasses that do paint enable the HasContents flag). This lets
Graphics View know whether there's any point in setting up the
world transform, opacity and other things.
Reviewed-by: Lars
|
|
|
|
| |
Regression introduced during refactoring earlier today.
|
|
|
|
|
|
|
|
|
| |
The code so far was converting the rect to a painterpath, mapping
that one and then taking the bounding rect. It is actually sufficient
to simply map the four corners of the rectangle and take the bounding
rect of these four points even in the projective case.
Reviewed-by: Andreas
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Greatly simplify how we handle opacity and store it as a member in
QGraphicsItemPrivate. Remove the caching of effectiveOpacity. It's
faster to calculate it on the fly, and the recursive painting algorithm
will make even that need go away.
Reviewed-by: Andreas
|
|
|
|
|
|
|
|
| |
Since the transform is now a pointer in QGraphicsItemPrivate, we can
use this pointer directly and there's no need for a separate bitflag
anymore.
Reviewed-by: Andreas
|
|
|
|
|
|
|
|
|
| |
Now that we have a recursive painting algorithm these types of
optimizations are no longer necessary. In fact they only cause more
problems and clutter up the code unnecessarily. Removing this also
removes extra overhead from moving and transforming items.
Reviewed-by: Lars
|
|
|
|
|
|
|
|
|
|
|
| |
Removed some experimental code to handle scaling and rotating around
different axis. It cuased setTransform and transform not to behave
symmetrically and caused some performance regressions.
Additionally moved the QTransform out of the (relatively slow) extra
list and made it a pointer in QGraphicsItemPrivate.
Reviewed-by: Andreas
|
|
|
|
|
|
|
|
|
|
|
| |
This is work-in-progress, so don't expect everything to work perfectly.
Most of the auto-test pass and examples and demos seem to run fine.
Unfortunately I'm too tired to write about the actual update mehanism
now, but it's faster than the old approach (if that helps:)). There's
more to optimize, but I'll come back to that later. I need some sleep now :)
To be continued.
|
|
|
|
| |
We'll need this later when making a smarter update mechanism.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
the important thing is by effectively implementing Simple Canvas' approach
to drawing, we're in theory (and in practise measured on the desktop)
as fast as Simple Canvas when rendering.
|
|
|
|
|
|
|
|
| |
Moving qpaintengineex_opengl2_p.h down caused it to come after
an include of <X11/Xlib.h>, which causes problems on some platforms.
Move it back up again.
Reviewed-by: trustme
|
|
|
|
| |
Reviewed-by: trustme
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
This compiler doesn't seem to follow the same rule as others
for implicit conversions to/from wchar_t.
Add the necessary casts, keeping in mind that sizeof(wchar_t) == 2
on Windows.
|
| |
| |
| |
| | |
Reviewed-by: trustme
|
|/
|
|
| |
Reviewed-by: trustme
|
|
|
|
|
|
|
|
|
|
|
| |
Thunderbird sets only the user level shell association for mailto. This
is now being read before the default mail application registry.
The registry crawling could have been avoided by using the ShellExecute()
but it supports only around 2KBytes of data as parameter, so we will
continue using CreateProcess().
Task-number: 251554
Reviewed-by: Jens Bache-Wiig
|
|
|
|
| |
Reviewed-by: ogoffart
|
|
|
|
|
|
| |
That reduces memory usage.
Reviewed-by: denis
|
|
|
|
|
|
| |
range.
Reviewed-By: TrustMe
|
|
|
|
|
|
|
|
|
|
|
| |
When using Qt/E with VNC screen driver on top of the Linux framebuffer
(export QWS_DISPLAY="VNC:LinuxFb") the region to be exposed needs be clipped
to the real screen to avoid possible negative coordinates which in turn
cause access to invalid memory locations when comparing the content of the
VNC buffer with the Linux framebuffer.
Merge-request: 603
Reviewed-by: Tom Cooksey <thomas.cooksey@nokia.com>
|
| |
|
|
|
|
| |
Reviewed-by: Pierre
|
|
|
|
|
| |
I didn't test this, because I can't build qdoc3 due to changes in
QStringBuilder.
|
|
|
|
|
|
|
|
|
| |
still paint them.
The autotest is included.
Task-number: 254449
Reviewed-by: ogoffart
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This enables the antialiazing to be done on the graph as a whole, and
not on every tiny line segment. The result is that the curve is painter
prettier.
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Draw the curve with anti-aliasing.
Do not use absolute black, but rather a dark black color for the lines.
Draw the red and blue dots, indicating the start and end points.
Reviewed-by: Jan-Arve
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
In case the SetWindowRgn() fails, the region object has to be deleted.
Task-number: 251293
Reviewed-by: Denis Dzyubenko
|