| Title: | DOCUMENT T1.0 |
| Notice: | **New notesfile (DOCUMENT.NOTE) now available (see note 897)** |
| Moderator: | CLOSET::ADLER |
| Created: | Mon Feb 09 1987 |
| Last Modified: | Thu Oct 31 1991 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 897 |
| Total number of notes: | 4397 |
SUGGESTION: Change the point size of a <SUBCOMMAND> title so that you
can distinguish it from a <COMMAND> title.
Using: doctype: layered
device: mail, ln03
template: Command Template
The point size of a <COMMAND> title (the size of the command name
under the line that runs across the page) is the same as the point
size of a <SUBCOMMAND> title. This is okay as long as you have a page
break that separates the commands from the subcommands. However, in
BL06-BL08 you have given us the ability to turn off page breaks for
commands and subcommands.
I have found an application where I need to use commands and
subcommands without page breaks; command descriptions aren't large
enough to warrent a whole page. My problem is that you cannot
distinguish the command from the surrounding subcommands if you have
more than one to a page. The running heads help, but I feel that you
also need a visual cue.
--Gerry
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 539.1 | DSSDEV::FISHER | Work that dream and love your life. | Mon Jun 22 1987 12:12 | 17 | |
SUGGESTION: If you are going to give us the ability to place several <COMMAND>s or <SUBCOMMAND>s on a single page, then it would be handy to be able to suppress the command's running head. Currently, you place the command title of the last command on the page in the running head. This is misleading. It implies that there are no other commands documented on that page. It would be more useful to allow me to use a subsection header (Output Functions, Input Functions, Memory Allocation Routines, and so forth) and to suppress the <COMMAND> or <SUBCOMMAND> as the second running head. That way, the user can locate the category and then scan each page to find the routine description (the individual routine's name would also be listed in the TOC). --Gerry | |||||