| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Reviewed-by: Trust Me
|
|
|
|
|
|
|
| |
Trying to fix QTBUG-6563, getting crash from cut-n-paste slippage, now fixed.
Task-number: QTBUG-6563
Reviewed-by: Rhys Weatherley
|
|
|
|
|
|
| |
Definitely a compiler bug.
Reviewed-by: Kent Hansen
|
|
|
|
|
|
|
|
| |
The QImagePixmapCleanupHooks instance was never deleted. Fixed by making
it a Q_GLOBAL_STATIC.
Task-number: QTBUG-6116
Reviewed-by: Trond
|
|
|
|
|
|
|
| |
Better than having to befriend QPixmapData and setting is_cached
manually.
Reviewed-by: Tom Cooksey
|
|
|
|
| |
Reviewed-By: TrustMe
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Before the QExplicitlySharedDataPointer change, the ref-count was 0 when
calling the cleanup hooks from ~QPixmap. That enabled the hook to figure
out if the pixmap is being modified or deleted. As the ref count is now
1 when calling the cleanup hooks in ~QPixmap, we need to seperate the
hooks.
This change should make using textre-from-pixmap faster as the EGL/glX
surface wont get re-created everytime the pixmap is modified.
Reviewed-By: Gunnar
|
|
|
|
| |
Reviewed-by: Trust Me
|
|
|
|
| |
Reviewed-by: Trust Me
|
|
|
|
| |
Reviewed-by: Trust Me
|
| |
|
|
The new class alows more than one hook to be installed at a time and,
for QPixmaps, the hook is told which pixmap is getting deleted.
Reviewed-By: Samuel
|