summaryrefslogtreecommitdiffstats
path: root/src/multimediakit/video/qabstractvideobuffer.cpp
diff options
context:
space:
mode:
Diffstat (limited to 'src/multimediakit/video/qabstractvideobuffer.cpp')
-rw-r--r--src/multimediakit/video/qabstractvideobuffer.cpp6
1 files changed, 0 insertions, 6 deletions
diff --git a/src/multimediakit/video/qabstractvideobuffer.cpp b/src/multimediakit/video/qabstractvideobuffer.cpp
index 8704e40fc..88c00f6a5 100644
--- a/src/multimediakit/video/qabstractvideobuffer.cpp
+++ b/src/multimediakit/video/qabstractvideobuffer.cpp
@@ -55,8 +55,6 @@ QT_BEGIN_NAMESPACE
video data. Creating a subclass of QAbstractVideoBuffer will allow you to construct video
frames from preallocated or static buffers.
- XXX where do these come from?
-
The contents of a buffer can be accessed by mapping the buffer to memory using the map()
function which returns a pointer to memory containing the contents of the the video buffer.
The memory returned by map() is released by calling the unmap() function.
@@ -64,8 +62,6 @@ QT_BEGIN_NAMESPACE
The handle() of a buffer may also be used to manipulate its contents using type specific APIs.
The type of a buffer's handle is given by the handleType() function.
- XXX example of handle stuff (opengl etc)
-
\sa QVideoFrame
*/
@@ -194,8 +190,6 @@ QAbstractVideoBuffer::HandleType QAbstractVideoBuffer::handleType() const
The type of the handle is given by handleType() function.
- XXX put a table here too
-
\since 1.0
\sa handleType()
*/