Thanks for evaluating QVCS.  Leave these tips enabled for some useful hints about QVCS features.
You can change the default project settings for all projects by selecting the "Default QVCS Project" and then selecting Project/Edit from the menu.
You can add your own QVCS tips by editing the tips.txt file in the QVCS executable directory.
If you want to use the $Version$ keyword, make sure to get any files containing it after you've applied the version label.
You can click the Cancel button to stop multiple file operations.
You can double click the column heading boundaries to resize the column to the maximum width of the column contents.
If a file icon is yellow, it means that the newest revision for that file is newer than your copy of that file.
Floating labels are a powerful way to manage and group QVCS archives.  See the "floating labels" glossary entry.
You can type CTRL-A to select all the files in the file window.
Embedding spaces in QVCS user names will cause problems if you use QVCS on DOS machines that support only 8.3 filenames.  Instead of spaces, use capitalization instead.
QVCS can expand keywords in your source code making it easy to add audit trail information to your source.
When journaling is enabled for a QVCS archive, any change to that archive will cause QVCS to add an entry to the project journal file.
You can enable and disable QVCS archive attributes (like keyword expansion, or journaling) separately for each archive.
QVCS supports "branching".  See the "Branching" help topic for more information.
You can customize the text that QVCS substitutes when it expands the $Copyright$ keyword.  See the Copyright help index entry for more information.
You can change the sort order of the revisions that appear in the history pane from the History/Sort... menu.
You can filter the revisions that appear in the history pane from the History/Filter... menu.
The QVCS help file (qwin3.hlp) has a glossary of QVCS terms.  Check the index for the "Glossary" entry.
The $LogX$ keyword allows you to show just the X most recent revisions in the expanded log.  For example, $Log3$ shows info for just the 3 most recent revisions.
Locking a QVCS archive doesn't change the file read/write attributes of the workfile.
You can use the qmerge command line utility to merge two different sets of edits of the same file.
The only way to delete revisions from a QVCS archive is with the qdelrev command line utility.
QVCS doesn't pollute your registry with ANY entries.
Uninstalling QVCS is as simple as deleting the QVCS executables.
Take a look at the "Understanding..." help topics.  They explain some useful project related topics.
The QVCS archive file format is documented in qwin3.hlp.  See the "QVCS Archive File Format" for details.
The "Advanced" button on the "Label file" dialog allows you to create a "floating" label, or to duplicate an existing label.
You can change the comment associated with a revision from the File/Modify Revision/Description menu.
You can change the author associated with a revision from the File/Modify Revision/Author menu.
You can refresh the information on the screen by pressing the F5 key.
A "floating label" always points to the most recent revision on the branch that it's associated with.
After you edit a file that you've checked out, the lock symbol on the file list display will change to include a small green "delta" after a project refresh (F5).
If the default branch for an archive is different than the TRUNK, QWin3 will display a small "tree" bitmap for that archive, instead of the normal file bitmap.
QVCS stores the access list for an archive within the archive itself.
Changing the access list for a project doesn't change the access list for any existing archives in the project.
To change the access list for all the archives in a project, select the "Project/Modify Archive/Access List" menu command.
If you use keyword expansion, have archive caching enabled, and work in a team, you should try to make sure that all your projects point to the UNC named location for your archives so that all users will have the same keyword expansion for those keywords that refer to the archive location (like the $Log$ keyword).
