(In a perfect world, this file will be empty.)

Known bugs as of version 1.3a.  Please do not report these (patches are
more than welcome).

  - When resizing the window, no check is being done to see if the
    "More" prompt should be removed.

  - Using block-justified text with Tads 3 games works, but the text is
    not justified correctly.  This is because doublespacing can't be
    turned off in the new Tads 3 VM and the Qt text renderer works buggy
    with doublespaced block-justified text.

  - Deleting themes works, but garbage is left in the configuration
    file (~/.qt/qtadsrc).  It's harmless, but not nice.  (Hey, maybe I
    can get away with it by saying that it's not a bug but a feature;
    the garbage serves backup-purposes! ;)

  - Pasting text that contains line-breaks into the main window won't
    work.

  - If a command that is recalled from the history causes the window to
    scroll (because it's more than one line long), display problems can
    occur (some text disappears).  This seems to be a bug in Qt.

  - The number of underscores (_) QTads outputs when the game prints a
    <hr> tag is fixed, no matter how wide the window is.

  - The Tads 3 game "Max Blaster and Doris de Lightning ..." doesn't
    work with QTads.  I don't know why though (I guess it relies on
    banners; they're not supported yet).  This game will crash QTads.

  - When an attempt is made to scroll the text manually while
    autoscrolling is active (that is, when the interpreter is currently
    scrolling newly displayed text), autoscrolling is not halted, but
    tries to scroll down to the last line of text.


Bug-like things that aren't QTads' fault and therefore can't be fixed:

  - The "Doublespace" option in the configuration dialog doesn't work
    with Tads 3 games.  This is because doublespacing is handled by the
    game itself, not by a virtual machine mechanism.

  - On some systems, QTads (like any other Qt application on such a
    system) generates mysterious warning messages from the X server.
    Seems to be a bug in Qt.  Although the warnings should be ignored,
    they are very annoying.  Sometimes the problem goes away by
    recompiling the Qt library with the font anti-aliasing support
    disabled (but I don't recommend this; without anti-aliasing, text
    is ugly as hell).
