summaryrefslogtreecommitdiffstats
path: root/doc/html/ntqbuffer.html
diff options
context:
space:
mode:
authorMichele Calgaro <michele.calgaro@yahoo.it>2024-06-08 12:56:43 +0900
committerMichele Calgaro <michele.calgaro@yahoo.it>2024-06-08 12:56:43 +0900
commit0cf411b09cf5d8970b873a338a69eae98d5ce5d8 (patch)
tree107cf55759cc3138bb1e0035b479bcd92127403a /doc/html/ntqbuffer.html
parente6077c30d14e9d662e8843c554db86c0d366d0b6 (diff)
downloadtqt3-0cf411b09cf5d8970b873a338a69eae98d5ce5d8.tar.gz
tqt3-0cf411b09cf5d8970b873a338a69eae98d5ce5d8.zip
Rename text nt* related files to equivalent tq*
Signed-off-by: Michele Calgaro <michele.calgaro@yahoo.it>
Diffstat (limited to 'doc/html/ntqbuffer.html')
-rw-r--r--doc/html/ntqbuffer.html8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/html/ntqbuffer.html b/doc/html/ntqbuffer.html
index b18b2fbe..0472498a 100644
--- a/doc/html/ntqbuffer.html
+++ b/doc/html/ntqbuffer.html
@@ -55,7 +55,7 @@ The TQBuffer class is an I/O device that operates on a <a href="qbytearray.html"
<p>
<p> TQBuffer is used to read and write to a memory buffer. It is
-normally used with a <a href="ntqtextstream.html">TQTextStream</a> or a <a href="ntqdatastream.html">TQDataStream</a>. TQBuffer has an
+normally used with a <a href="tqtextstream.html">TQTextStream</a> or a <a href="ntqdatastream.html">TQDataStream</a>. TQBuffer has an
associated TQByteArray which holds the buffer data. The <a href="ntqiodevice.html#size">size</a>() of
the buffer is automatically adjusted as data is written.
<p> The constructor <tt>TQBuffer(TQByteArray)</tt> creates a TQBuffer using an
@@ -66,16 +66,16 @@ array because TQByteArray is <a href="shclass.html">explicitly
<p> Use <a href="ntqiodevice.html#open">open</a>() to open the buffer before use and to set the mode
(read-only, write-only, etc.). <a href="ntqiodevice.html#close">close</a>() closes the buffer. The
buffer must be closed before reopening or calling setBuffer().
-<p> A common way to use TQBuffer is through <a href="ntqdatastream.html">TQDataStream</a> or <a href="ntqtextstream.html">TQTextStream</a>, which have constructors that take a TQBuffer
+<p> A common way to use TQBuffer is through <a href="ntqdatastream.html">TQDataStream</a> or <a href="tqtextstream.html">TQTextStream</a>, which have constructors that take a TQBuffer
parameter. For convenience, there are also TQDataStream and
-<a href="ntqtextstream.html">TQTextStream</a> constructors that take a <a href="qbytearray.html">TQByteArray</a> parameter. These
+<a href="tqtextstream.html">TQTextStream</a> constructors that take a <a href="qbytearray.html">TQByteArray</a> parameter. These
constructors create and open an internal TQBuffer.
<p> Note that TQTextStream can also operate on a <a href="tqstring.html">TQString</a> (a Unicode
string); a TQBuffer cannot.
<p> You can also use TQBuffer directly through the standard <a href="ntqiodevice.html">TQIODevice</a>
functions <a href="ntqiodevice.html#readBlock">readBlock</a>(), <a href="#writeBlock">writeBlock</a>() <a href="ntqiodevice.html#readLine">readLine</a>(), <a href="ntqiodevice.html#at">at</a>(), <a href="ntqiodevice.html#getch">getch</a>(),
<a href="ntqiodevice.html#putch">putch</a>() and <a href="ntqiodevice.html#ungetch">ungetch</a>().
-<p> <p>See also <a href="ntqfile.html">TQFile</a>, <a href="ntqdatastream.html">TQDataStream</a>, <a href="ntqtextstream.html">TQTextStream</a>, <a href="qbytearray.html">TQByteArray</a>, <a href="shclass.html">Shared Classes</a>, <a href="collection.html">Collection Classes</a>, and <a href="io.html">Input/Output and Networking</a>.
+<p> <p>See also <a href="ntqfile.html">TQFile</a>, <a href="ntqdatastream.html">TQDataStream</a>, <a href="tqtextstream.html">TQTextStream</a>, <a href="qbytearray.html">TQByteArray</a>, <a href="shclass.html">Shared Classes</a>, <a href="collection.html">Collection Classes</a>, and <a href="io.html">Input/Output and Networking</a>.
<hr><h2>Member Function Documentation</h2>
<h3 class=fn><a name="TQBuffer"></a>TQBuffer::TQBuffer ()