From c0780a876e11732962b98e3b1aac0f503b4e9ad9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Sl=C3=A1vek=20Banko?= Date: Fri, 8 Nov 2013 09:46:27 +0100 Subject: Revert "Update minor TQt3 tool names to match current TQt3 sources in GIT" --- doc/html/emb-qvfb.html | 26 +++++++++++++------------- 1 file changed, 13 insertions(+), 13 deletions(-) (limited to 'doc/html/emb-qvfb.html') diff --git a/doc/html/emb-qvfb.html b/doc/html/emb-qvfb.html index c2a301e..df971cc 100644 --- a/doc/html/emb-qvfb.html +++ b/doc/html/emb-qvfb.html @@ -1,5 +1,5 @@ - + @@ -34,17 +34,17 @@ body { background: #ffffff; color: black; }

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 $QTDIR/tools/tqvfb. +

The virtual framebuffer is located in $QTDIR/tools/qvfb.

Using the Virtual Framebuffer

    -
  1. Configure Qt/Embedded with the -tqvfb argument and compile the library: +
  2. Configure Qt/Embedded with the -qvfb argument and compile the library: 
    -    ./configure -tqvfb
+    ./configure -qvfb
     make
    -
  3. Compile tqvfb as a normal Qt/X11 application and run it. Do not +
  4. Compile qvfb as a normal Qt/X11 application and run it. Do not compile it as a Qt/Embedded application.
  5. Start a Qt/Embedded master application (i.e., construct QApplication with the QApplication::GuiServer flag or use the -qws command line parameter). You can specify to the server that @@ -53,13 +53,13 @@ you wish to use the virtual framebuffer driver, e.g.: masterapp -qws -display QVFb:0 -
  6. Qt/Embedded will autodetect tqvfb, so you can omit the -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, +
  7. Qt/Embedded will autodetect qvfb, so you can omit the -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.)

-

tqvfb supports the following command line options: +

qvfb supports the following command line options:

@@ -82,23 +82,23 @@ display will be corrupted.)

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 (tqvfb). The regions of the display that have changed are updated +window (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 View|Refresh Rate -menu item. This will cause tqvfb to check for updated regions more +menu item. This will cause 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 tqvfb will compete for +be frequent, then the application and qvfb will compete for processor time.

Mouse and keyboard events are passed to the Qt/Embedded master process via 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 -tqvfb. +in a production environment; do not configure production libraries with -qvfb.

-- cgit v1.2.1
Option Meaning