summaryrefslogtreecommitdiffstats
path: root/doc/qvfb.doc
diff options
context:
space:
mode:
authorSlávek Banko <slavek.banko@axis.cz>2013-11-08 09:46:27 +0100
committerSlávek Banko <slavek.banko@axis.cz>2013-11-08 09:46:27 +0100
commitc0780a876e11732962b98e3b1aac0f503b4e9ad9 (patch)
tree3868825a8f2ab785cb308248a8e88942610f5a6f /doc/qvfb.doc
parentef73e104bd71560e1dab2c0c9a1bb1d718674e1a (diff)
downloadqt3-c0780a876e11732962b98e3b1aac0f503b4e9ad9.tar.gz
qt3-c0780a876e11732962b98e3b1aac0f503b4e9ad9.zip
Revert "Update minor TQt3 tool names to match current TQt3 sources in GIT"
Diffstat (limited to 'doc/qvfb.doc')
-rw-r--r--doc/qvfb.doc26
1 files changed, 13 insertions, 13 deletions
diff --git a/doc/qvfb.doc b/doc/qvfb.doc
index e63ba51..7bc1546 100644
--- a/doc/qvfb.doc
+++ b/doc/qvfb.doc
@@ -36,24 +36,24 @@
**
**********************************************************************/
-/*! \page emb-tqvfb.html
+/*! \page emb-qvfb.html
\title Qt/Embedded Virtual Framebuffer
The virtual framebuffer allows Qt/Embedded programs to be developed on
a desktop machine, without switching between consoles and X11.
-The virtual framebuffer is located in \c $QTDIR/tools/tqvfb.
+The virtual framebuffer is located in \c $QTDIR/tools/qvfb.
\section1 Using the Virtual Framebuffer
\list 1
-\i Configure Qt/Embedded with the \c -tqvfb argument and compile the library:
+\i Configure Qt/Embedded with the \c -qvfb argument and compile the library:
\code
- ./configure -tqvfb
+ ./configure -qvfb
make
\endcode
-\i Compile \c tqvfb as a normal Qt/X11 application and run it. Do \e not
+\i Compile \c qvfb as a normal Qt/X11 application and run it. Do \e not
compile it as a Qt/Embedded application.
\i Start a Qt/Embedded master application (i.e., construct
QApplication with the QApplication::GuiServer flag or use the \c
@@ -62,15 +62,15 @@ The virtual framebuffer is located in \c $QTDIR/tools/tqvfb.
\code
masterapp -qws -display QVFb:0
\endcode
-\i Qt/Embedded will autodetect tqvfb, so you can omit the \c -display
- command line parameter if you know that tqvfb is running, and that
- the Qt/Embedded library supports tqvfb. (If this is not the case,
+\i Qt/Embedded will autodetect qvfb, so you can omit the \c -display
+ command line parameter if you know that qvfb is running, and that
+ the Qt/Embedded library supports qvfb. (If this is not the case,
Qt/Embedded will write to the real framebuffer, and your X11
display will be corrupted.)
\endlist
-\c tqvfb supports the following command line options:
+\c qvfb supports the following command line options:
\table
\header \i Option \i Meaning
@@ -95,18 +95,18 @@ The virtual framebuffer is located in \c $QTDIR/tools/tqvfb.
The virtual framebuffer emulates a framebuffer using a shared memory region
(the virtual frame buffer) and a utility to display the framebuffer in a
-window (\c tqvfb). The regions of the display that have changed are updated
+window (\c qvfb). The regions of the display that have changed are updated
periodically, so you will see discrete snapshots of the framebuffer rather
than each individual drawing operation. For this reason drawing problems
such as flickering may not be apparent until the program is run using a real
framebuffer.
The target refresh rate can be set via the <b>View|Refresh Rate</b>
-menu item. This will cause \c tqvfb to check for updated regions more
+menu item. This will cause \c qvfb to check for updated regions more
frequently. The rate is a target only. If little drawing is being
done, the framebuffer will not show any updates between drawing
events. If an application is displaying an animation the updates will
-be frequent, then the application and \c tqvfb will compete for
+be frequent, then the application and \c qvfb will compete for
processor time.
Mouse and keyboard events are passed to the Qt/Embedded master process via
@@ -114,6 +114,6 @@ named pipes.
The virtual framebuffer is a development tool only. No security issues have
been considered in the virtual framebuffer design. It should be avoided
-in a production environment; do not configure production libraries with \c -tqvfb.
+in a production environment; do not configure production libraries with \c -qvfb.
*/