RiverWare Links to External RPL Documents (November 2008)
File Type Association Manager

The RiverWare File Type Association Manager is used to specify the executable programs used for Viewing and Editing documents of the four supported Format Types (HTML, PDF, Word, or Text). The Executable File Paths are stored with the User's Account (using Qt QSettings).

Settings Menu:

Executable file paths can be edited (including pasting from the system clipboard) by double clicking an item within the Executable column, or can be picked with a File Selector by clicking the folder icon. On Windows, all of the executable file paths can be set to the default executables associated with the user's account using the "Settings >> Set Default Executables" menu operation. Changes can either be saved (by clicking OK or Apply) or dropped (by clicking Restore or Cancel).

If the ACROREAD_PATH environment variable is defined, the PDF View item is set to the value of that variable, is non-editable, and is shown with a grey background.

The "[X] Support anchors for Edit operations" checkbox is not operable. Currently, when opening a Rpl Object External Document for Editing, the anchor text (used to automatically scroll to a particular section within the document) is not supported. However, the name of the Rpl Object name text is copied to the system clipboard -- this can be used to paste into the "Search" function within the editor or viewer program.

Technical note: The "Set Default Executables" feature depends on the presence of the following four files in the RiverWare program directory, or the ability of RiverWare to create these files:

  • empty.html
  • empty.pdf
  • empty.doc
  • empty.txt

The content of those files is not significant. In fact, the distributed copies, or those generated by RiverWare are empty (0 bytes).
 
Potential Feature -- NOT WORKING [11-2-2008]:  The intention was that it would be technically possible to append constant command line parameters (to the executable program) after the program executable file path text. However no useful parameters have been identified for any of the tested applications. It turns out that there's a problem with the current implementation: When launching the executable, command line parameters need to be conveyed to the application in a separate field. [See RiverWare method, DocumentInfo::startDetached()].

---