mfbcap.5

spice中支持多层次元件模型仿真的可单独运行的插件源码

The format for setting a pixel in the current color at the x,y pixel
coordinate is defined by the \fBWPX\fR format string.
.PP
The format for drawing a circle with its center at the x,y pixel
coordinate and having a radius of z pixels is defined by the
\fBDCS\fR format string.
.PP
The format for clearing the entire screen to the current color is
given by the \fBGCS\fR format string.  If there is no such command sequence,
it may be substituted by the command sequence that will write a solid box
in the current color over the entire screen.
.PP
There are three format strings for
defining the terminal's polygon command sequence.  First the \fBPLS\fR starting
sequence is used to define x,y as the first of z pixel coordinates.
This character sequence will be followed by z-1 occurrences of the \fBPLV\fR
format string which defines the remaining vertices of the polygonal path.
Finally, an ending sequence that is defined by the \fBPLE\fR format
string terminates the polygon sequence.  For terminals
which have inconsistent formats for drawing solid polygons,
the \fBPLSOL\fR sequence may be used in place of the \fBPLS\fR
sequence.  If the terminal is capable of drawing a filled polygon in the
current fill pattern, then the \fBFPOLY\fR boolean should appear in the
.I MFBCAP
entry.
.PP
.ne 5
.B Video Layer Table
.PP
If the terminal has a video layer table, then the \fBVLT\fR boolean
must be present in the 
.I MFBCAP
entry.
.I MFBCAP
assumes that the VLT uses the red-green-blue system for defining colors.
If the \fBHLS\fR boolean capability is specified, then the RGB arguments
become HLS (hue-lightness-saturation) values.
The maximum intensity of red, green, or blue in the VLT (or the
lightness or saturation if using the HLS system) is given by
the \fBVTI\fR numeric capability.  The format for setting a particular
entry of the VLT is given by the \fBVTE\fR format string.
The \fBVTL\fR numeric value can be used to define the length of the
VLT in terms of the number of bit planes.
.PP
.ne 5
.B Defining Styles
.PP
The \fBLDS\fR string capability defines the sequence for (re)defining
a line style corresponding to a particular style ID.  The \fBLDF\fR
format string is used to define an eight bit mask that represents
the new line style.  The \fBLDE\fR format string terminates the
definition of the new line style.
.PP
The definition of a new fill pattern is more complicated than is the case
for line styles.
It is necessary to transform an eight by eight intensity array into
whatever command syntax is required by the terminal.  The \fBFDS\fR string
capability is used to begin the (re)definition of a fill pattern.
The \fBFDF\fR format string defines one row or column of the fill pattern
using an eight bit mask (one row of the eight by eight intensity array).
If the \fBFDR\fR boolean is present, then it is assumed that the fill
pattern is being defined by rows in which case the \fBFDF\fR sequence
is sent by the number of times defined by the \fBFDH\fR numeric capability.
Otherwise, it is assumed that the fill pattern is defined by columns, and
the \fBFDF\fR sequence is sent by the number of times defined by the \fBFDW\fR
numeric capability.  If, for example, the number of rows in the fill pattern
is ten, the \fBFDF\fR sequence is first transmitted using each of the eight
rows of the initial eight by eight intensity array, and then the sequence is
sent twice using the first and second rows of the initial intensity array.
The \fBFDE\fR format string terminates the definition of the new fill pattern.
.PP
.ne 5
.B Raster Capabilities
.PP
There are four format strings for
defining the terminal's raster copy command sequence.
First the \fBRSCPS\fR starting
sequence is used to begin the raster copy command.
This character sequence will be followed the \fBRSSRC\fR
format string which defines the lower, left coordinate and length
and width of the source area and the \fBRSDST\fR format string
which defines the lower left coordinate and the length and width
of the destination area.
The \fBRSSRC\fR sequence appears first only if the \fBRSCSF\fR boolean
is defined.
Finally, an ending sequence that is defined by the \fBRSCPE\fR format
string terminates the raster copy sequence.
.PP
.ne 5
.B Graphic Text
.PP
.I MFBCAP
supports a single font graphic text.  The height and width of the
text font are given respectively by the \fBGCH\fR and \fBGCW\fR numeric
capabilities.  Graphics text is displayed with three format strings.
A text string with z characters with a lower left justification at the x,y
pixel coordinate is begun with the format string defined
by \fBGTS\fR.  This will be followed by the transmission of the z
characters and terminated by the format string defined by \fBGTE\fR.
The graphic text can offset from the current graphics position
by setting the numeric capabilities \fBGTH\fR and \fBGTW\fR.
The following figure demonstrates the assumed character font for the
two characters "gh".  The character "0" marks a pixel in the character font,
and the character "X" marks the x,y pixel coordinate
to which the two characters where justified.  Note that the \fBGCH\fR,
\fBGCW\fR, \fBGTH\fR, and \fBGTW\fR numeric capabilities must always be
non-negative integers.
.sp 1
.ne 16
.nf
.ta \w'XXXXXXXXXX'u +\w'X 'u +\w'X     'u +\w'X 'u +\w'X    'u +\w'X 'u +\w'X 'u +\w'X 'u +\w'X 'u +\w'X 'u +\w'X 'u +\w'XXXXX'u +\w'X 'u +\w'X 'u +\w'X 'u +\w'X 'u +\w'X 'u +\w'X 'u +\w'X 'u
		 		_	.	.	.	.	.	.   	0	.	.	.	.	.
		 		|	.	 	 	 	 	.   	0	 	 	 	 	.
		 		|	.	 	 	 	 	.   	0	 	 	 	 	.
		 		|	.	0	0	0	0	.   	0	0	0	0	 	.
		 		|	0	 	 	 	 	0   	0	 	 	 	0	.
		 		|	0	 	 	 	 	0   	0	 	 	 	 	0
		_	GCH	0	 	 	 	 	0   	0	 	 	 	 	0
		|		|	X	0	0	0	0	0   	0	 	 	 	 	0
		|		|	.	 	 	 	 	0   	.	 	 	 	 	.
	GTH		|	.	 	 	 	 	0   	.	 	 	 	 	.
		|		|	0	 	 	 	 	0   	.	 	 	 	 	.
		|		|	.	0	0	0	0	.   	.	.	.	.	.	.
		-		-
		 		 	|	-GCW-	|	-GTW-	|

.fi
.sp 1
.PP
If the terminal supports rotatable graphic text, then the \fBROT\fR
boolean is present in the
.I MFBCAP
entry.
If rotated text is desired the \fBRTS\fR character sequence is issued prior
to the the \fBGTS\fR sequence and defines a rotation of x degrees, where
x is between -360 and 360.
.PP
.I MFBCAP
supports two graphic text modes.  If the graphic text can be destructive,
then the \fBGTR\fR boolean is present in the
.I MFBCAP
entry, and the \fBRMO\fR format string specifies the character sequence
for entering the destructive graphic text mode.  If the terminal has
graphic text that can overstrike, then the \fBGTO\fR boolean is present
in the 
.I MFBCAP
entry, and the \fBOMO\fR format string defines the character sequence
for entering the overstriking graphic text mode.
.PP
.ne 5
.B Keyboard Control
.PP
For terminals with special keyboard/cursor operations, 
.I MFBCAP
provides a set of string capabilities for controlling keyboard input.
The keyboard is initialized, and the current graphics position is moved
to the x,y pixel coordinate by the \fBKYS\fR format string.
The current graphics position can
be offset upward from the above x,y pixel coordinate by setting values to
the \fBKYX\fR and \fBKYY\fR numeric capabilities.  The keyboard
backspace sequence is defined by the \fBKYB\fR format string (the is
NO default for the backspace format string).  The keyboard is
uninitialized by the \fBKYE\fR format string.
.PP
If the terminal does not have the above capabilities, a keyboard input
routine, such as that used in
.I mfb(3),
can use the terminals graphic text capabilities to echo keyboard characters
on a command line.
.PP
.ne 5
.B Pointing Device.
.PP
If the terminal has a pointing device, then the \fBPOD\fR boolean is present
in the
.I MFBCAP
entry.  If the pointing device has buttons, then the \fBPDB\fR boolean
is set, the number of buttons is given by the \fBNPB\fR numeric capability,
and the values returned by the respective buttons of the
pointing device are defined by the \fBBU1\fR through \fBBU12\fR numeric
capabilities.
.PP
The graphics pointing device is initialized with the \fBPDS\fR format
string.  The \fBPDR\fR format string places the terminal in a waiting
mode until the first graphic input.  When this event occurs, the locator
event is decoded by the \fBPDF\fR format string.  The graphic pointing device
is uninitialized by the \fBPDE\fR format string.
.PP
If the \fBPRI\fR boolean
is set, one character is read immediately after the pointing device
initialization sequence \fBPDS\fR and before the pointing device is enabled
by \fBPDR\fR.  This is useful for terminals that have a cursor and can read
its current position but do not have the capability
of a graphic event (
.I i.e.,
an x,y pixel coordinate that is read immediately
after a key or button is pushed on the terminal).
.PP
The pointing device encoding format string \fBPDF\fR must assume that
the pointing device will send one signature character.  After the
pointing is activated by the \fBPDR\fR format string, the first
character transmitted from the terminal must be identical to the first
character of the \fBPDF\fR format string.  If the characters do not match,
then the
.I MFBDecode
routine used by
.I mfb(3)
will return the first character that was transmitted by the terminal.
.PP
The \fBPRBON\fR string capability defines the character sequence
to enable rubber banding of the pointing device, and \fBPRBOFF\fR
disables the rubber banding. 
.I MFBCAP
assumes that the center of rubber banding is the current graphics
position that can be defined by the \fBMPS\fR format string defined above.
.PP
.ne 5
.B Special Modes
.PP
If the graphics device is to be handled as a TTY, then the \fBTTY\fR
boolean must be present in the
.I MFBCAP
entry.  If the graphics encoding can produce 8 bit, nonASCII characters,
then the \fB8BB\fR boolean must be included.
If the graphics device is a TTY and is to be driven in a
.I RAW
mode, then the \fBRAW\fR boolean must be included.  See the manual for
.I tty(4).
Typically, this mode is used only if the device has no keyboard.
.PP
.I MFBCAP
supports four ALU writing modes.  These are the modes in which a pixel
is updated when written over.  The four possible modes are JAM (replace
mode), OR, EOR, and NOR.  The sequences for setting these modes are
\fBALUJAM\fR, \fBALUOR\fR, \fBALUEOR\fR, and \fBALUNOR\fR respectively.
.PP
.ne 5
.B Similar Terminals
.PP
If there are two very similar terminals, one can be defined as being
like the other but with certain exceptions.  The string capability
\fBMCE\fR is given with the name of the similar terminal.  The \fBMCE\fR
must be the last capability defined in the entry, and the combined length
of the two entries must not exceed 4096 characters.  Because
.I mfb
routines scan the entry from left to right, and because the \fBMCE\fR
entry is replaced by the corresponding entry, the capabilities given
on the left override identical capabilities defined for the similar terminal.
This is useful for defining different modes for a terminal, or for 
defining terminals with different peripherals.
.sp 1
.ne 2
.SH FILES
.DT
~cad/lib/mfbcap	    file containing terminal descriptions
.ne 2
.SH SEE ALSO
termcap(5), mfb(3), kic(CAD1)
.ne 2
.SH AUTHOR
Giles Billingsley 
.ne 7
.SH BUGS
.PP
The total length of a single entry (excluding only escaped new lines)
may not exceed 8192.
.PP
There is a restriction that allows a simple parser to be used for the
.I MFBCAP
file.  The delimiter is assumed to be a comma that is not immediately
preceded by a slash (\\) character.  String capabilities that terminate
with a slash character (as is the case for the vt125) must therefore separate
the delimiting comma and the slash character with a padding character.
.PP
Not all programs support all entries.
There are entries that may not be used by any program.