The QBuffer class provides a QIODevice interface for a QByteArray. More...
#include <QBuffer>
Inherits: QIODevice.
Note: All functions in this class are reentrant.
QBuffer ( QObject * parent = 0 ) | |
QBuffer ( QByteArray * byteArray, QObject * parent = 0 ) | |
~QBuffer () | |
QByteArray & | buffer () |
const QByteArray & | buffer () const |
const QByteArray & | data () const |
void | setBuffer ( QByteArray * byteArray ) |
void | setData ( const QByteArray & data ) |
void | setData ( const char * data, int size ) |
virtual bool | atEnd () const |
virtual bool | canReadLine () const |
virtual void | close () |
virtual bool | open ( OpenMode flags ) |
virtual qint64 | pos () const |
virtual bool | seek ( qint64 pos ) |
virtual qint64 | size () const |
virtual qint64 | readData ( char * data, qint64 len ) |
virtual qint64 | writeData ( const char * data, qint64 len ) |
The QBuffer class provides a QIODevice interface for a QByteArray.
QBuffer allows you to access a QByteArray using the QIODevice interface. The QByteArray is treated just as a standard random-accessed file. Example:
QBuffer buffer; char ch; buffer.open(QBuffer::ReadWrite); buffer.write("Qt rocks!"); buffer.seek(0); buffer.getChar(&ch); // ch == 'Q' buffer.getChar(&ch); // ch == 't' buffer.getChar(&ch); // ch == ' ' buffer.getChar(&ch); // ch == 'r'
By default, an internal QByteArray buffer is created for you when you create a QBuffer. You can access this buffer directly by calling buffer(). You can also use QBuffer with an existing QByteArray by calling setBuffer(), or by passing your array to QBuffer's constructor.
Call open() to open the buffer. Then call write() or putChar() to write to the buffer, and read(), readLine(), readAll(), or getChar() to read from it. size() returns the current size of the buffer, and you can seek to arbitrary positions in the buffer by calling seek(). When you are done with accessing the buffer, call close().
The following code snippet shows how to write data to a QByteArray using QDataStream and QBuffer:
QByteArray byteArray; QBuffer buffer(&byteArray); buffer.open(QIODevice::WriteOnly); QDataStream out(&buffer); out << QApplication::palette();
Effectively, we convert the application's QPalette into a byte array. Here's how to read the data from the QByteArray:
QPalette palette; QBuffer buffer(&byteArray); buffer.open(QIODevice::ReadOnly); QDataStream in(&buffer); in >> palette;
QTextStream and QDataStream also provide convenience constructors that take a QByteArray and that create a QBuffer behind the scenes.
QBuffer emits readyRead() when new data has arrived in the buffer. By connecting to this signal, you can use QBuffer to store temporary data before processing it. For example, you can pass the buffer to QFtp when downloading a file from an FTP server. Whenever a new payload of data has been downloaded, readyRead() is emitted, and you can process the data that just arrived. QBuffer also emits bytesWritten() every time new data has been written to the buffer.
See also QFile, QDataStream, QTextStream, and QByteArray.
Constructs an empty buffer with the given parent. You can call setData() to fill the buffer with data, or you can open it in write mode and use write().
See also open().
Constructs a QBuffer that uses the QByteArray pointed to by byteArray as its internal buffer, and with the given parent. The caller is responsible for ensuring that byteArray remains valid until the QBuffer is destroyed, or until setBuffer() is called to change the buffer. QBuffer doesn't take ownership of the QByteArray.
If you open the buffer in write-only mode or read-write mode and write something into the QBuffer, byteArray will be modified.
Example:
QByteArray byteArray("abc"); QBuffer buffer(&byteArray); buffer.open(QIODevice::WriteOnly); buffer.seek(3); buffer.write("def", 3); buffer.close(); // byteArray == "abcdef"
See also open(), setBuffer(), and setData().
Destroys the buffer.
Reimplemented from QIODevice::atEnd().
Returns a reference to the QBuffer's internal buffer. You can use it to modify the QByteArray behind the QBuffer's back.
See also setBuffer() and data().
This is an overloaded function.
This is the same as data().
Reimplemented from QIODevice::canReadLine().
Reimplemented from QIODevice::close().
Returns the data contained in the buffer.
This is the same as buffer().
See also setData() and setBuffer().
Reimplemented from QIODevice::open().
Reimplemented from QIODevice::pos().
Reimplemented from QIODevice::readData().
Reimplemented from QIODevice::seek().
Makes QBuffer uses the QByteArray pointed to by byteArray as its internal buffer. The caller is responsible for ensuring that byteArray remains valid until the QBuffer is destroyed, or until setBuffer() is called to change the buffer. QBuffer doesn't take ownership of the QByteArray.
Does nothing if isOpen() is true.
If you open the buffer in write-only mode or read-write mode and write something into the QBuffer, byteArray will be modified.
Example:
QByteArray byteArray("abc"); QBuffer buffer; buffer.setBuffer(&byteArray); buffer.open(QIODevice::WriteOnly); buffer.seek(3); buffer.write("def", 3); buffer.close(); // byteArray == "abcdef"
If byteArray is 0, the buffer creates its own internal QByteArray to work on. This byte array is initially empty.
See also buffer(), setData(), and open().
Sets the contents of the internal buffer to be data. This is the same as assigning data to buffer().
Does nothing if isOpen() is true.
See also data() and setBuffer().
This is an overloaded function.
Sets the contents of the internal buffer to be the first size bytes of data.
Reimplemented from QIODevice::size().
Reimplemented from QIODevice::writeData().
© 2008-2011 Nokia Corporation and/or its subsidiaries. Nokia, Qt and their respective logos are trademarks of Nokia Corporation in Finland and/or other countries worldwide.
All other trademarks are property of their respective owners. Privacy Policy
Licensees holding valid Qt Commercial licenses may use this document in accordance with the Qt Commercial License Agreement provided with the Software or, alternatively, in accordance with the terms contained in a written agreement between you and Nokia.
Alternatively, this document may be used under the terms of the GNU Free Documentation License version 1.3 as published by the Free Software Foundation.