TREETEXT RELEASE HISTORY

Version 1.0.0 August 26th 1999

Initial version for public release, compiled with Microsoft Visual Basic 5.

Version 1.0.1 September 4th 1999

Minor bug fix release fixing the following problems:

(1) Moving an entry up using AltUp failed for the first child of a first child
(2) Usability problem: toolbar buttons within the outline and editing sets
were hidden rather than disabled if unavailable, causing them to appear in
different positions and making it difficult to click successively on the same
button
(3) Excessive flickering while entries were being moved using Alt and cursor
keys

Version 1.0.2 September 6th 1999

Minor bug fix release fixing the following problems:

(1) The red tag was lost on moving a tagged entry using the mouse, keyboard
or toolbar buttons.
(2) A very minor problem - the status bar was not being updated immediately
with the selected entry name if it was reenabled after being disabled.

Version 1.0.3 September 6th 1999

Minor bug fix release fixing the following problem:

(1) The red tag was lost on moving a child entry via its parent, parent's
parent etc.  A more elegant solution to the original problem has been
implemented, which caters for tagged entries at any level below the entry
being moved.

Version 1.1.0 September 7th 1999

Recompiled with Microsoft Visual Basic 6, using the latest Microsoft screen
controls and support files for improved speed and reliability.  No functional
changes since version 1.0.3.

Version 1.1.0 October 14th 1999

Help and printing enhancements

(1) HTML help file added according to the latest Microsoft standards,
replacing the previous Winhelp file
(2) Allow only the entry titles to be printed, with indentation, when
printing or previewing all entries, depending on the reply to a prompt.
(For technical reasons the indentation cannot safely be applied when the
entry texts were included, since text copied from external sources such as
emails could be protected, which would generate an error and prevent the
operation from working.)
(3) Prevent spurious blank lines from appearing if entry texts are blank
(4) Ensure that the correct default font is used when printing the entry
titles
