mfbcap.0

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

     There are three format strings for defining  the  terminal's
     polygon  command  sequence.  First the PLS 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 PLV format string which defines  the  remaining  ver-
     tices  of  the  polygonal path.  Finally, an ending sequence
     that is defined by the  PLE  format  string  terminates  the
     polygon  sequence.   For  terminals  which have inconsistent
     formats for drawing solid polygons, the PLSOL  sequence  may
     be  used  in  place of the PLS sequence.  If the terminal is
     capable of drawing a filled polygon in the current fill pat-
     tern,  then  the  FPOLY  boolean should appear in the _M_F_B_C_A_P
     entry.

     Video Layer Table

     If the terminal has  a  video  layer  table,  then  the  VLT
     boolean must be present in the _M_F_B_C_A_P entry.  _M_F_B_C_A_P assumes
     that the VLT uses the  red-green-blue  system  for  defining
     colors.   If  the  HLS 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 VTI numeric capability.  The format for set-
     ting a particular entry of the VLT is given by the VTE  for-
     mat string.  The VTL numeric value can be used to define the
     length of the VLT in terms of the number of bit planes.

     Defining Styles

     The  LDS  string  capability  defines   the   sequence   for
     (re)defining  a  line  style  corresponding  to a particular
     style ID.  The LDF format string is used to define an  eight
     bit mask that represents the new line style.  The LDE format



10






6/21/83                                                 MFBCAP(5)



     string terminates the definition of the new line style.

     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 FDS string
     capability is used to begin the  (re)definition  of  a  fill
     pattern.  The FDF 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 FDR boolean is
     present, then it is assumed that the fill pattern  is  being
     defined  by  rows  in which case the FDF sequence is sent by
     the number of times defined by the FDH  numeric  capability.
     Otherwise, it is assumed that the fill pattern is defined by
     columns, and the FDF sequence is sent by the number of times
     defined by the FDW numeric capability.  If, for example, the
     number of rows in the fill pattern is ten, the FDF  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  FDE  format  string  ter-
     minates the definition of the new fill pattern.

     Raster Capabilities

     There are four format strings for  defining  the  terminal's
     raster  copy  command  sequence.   First  the RSCPS starting
     sequence is used to begin the  raster  copy  command.   This
     character  sequence will be followed the RSSRC format string
     which defines the lower,  left  coordinate  and  length  and
     width  of  the source area and the RSDST format string which
     defines the lower left coordinate and the length  and  width
     of  the  destination area.  The RSSRC sequence appears first
     only if the RSCSF boolean is defined.   Finally,  an  ending
     sequence  that  is  defined  by the RSCPE format string ter-
     minates the raster copy sequence.

     Graphic Text

     _M_F_B_C_A_P supports a single font graphic text.  The height  and
     width of the text font are given respectively by the GCH and
     GCW 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 GTS.  This will be
     followed by the transmission of the z  characters  and  ter-
     minated  by  the  format string defined by GTE.  The graphic
     text can offset from the current graphics position  by  set-
     ting  the  numeric  capabilities GTH and GTW.  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



                                                               11






MFBCAP(5)                                                 6/21/83



     coordinate  to  which  the  two  characters where justified.
     Note that the GCH, GCW, GTH, and  GTW  numeric  capabilities
     must always be non-negative integers.

                         _    . . . . . .      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-  |



     If the terminal supports rotatable graphic  text,  then  the
     ROT boolean is present in the _M_F_B_C_A_P entry.  If rotated text
     is desired the RTS character sequence is issued prior to the
     the  GTS sequence and defines a rotation of x degrees, where
     x is between -360 and 360.

     _M_F_B_C_A_P supports two graphic text modes.  If the graphic text
     can  be  destructive, then the GTR boolean is present in the
     _M_F_B_C_A_P entry, and the RMO format string specifies the  char-
     acter  sequence  for  entering  the destructive graphic text
     mode.  If the terminal has graphic text that can overstrike,
     then the GTO boolean is present in the _M_F_B_C_A_P entry, and the
     OMO format string defines the character sequence for  enter-
     ing the overstriking graphic text mode.

     Keyboard Control

     For  terminals  with  special  keyboard/cursor   operations,
     _M_F_B_C_A_P 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 coordi-
     nate by the KYS format string.  The current  graphics  posi-
     tion  can  be offset upward from the above x,y pixel coordi-
     nate by setting values to the KYX and KYY numeric  capabili-
     ties.  The keyboard backspace sequence is defined by the KYB
     format string (the is NO default for  the  backspace  format
     string).   The  keyboard  is uninitialized by the KYE format
     string.

     If the terminal does not have the above capabilities, a key-
     board  input  routine,  such as that used in _m_f_b(_3), can use



12






6/21/83                                                 MFBCAP(5)



     the terminals graphic text  capabilities  to  echo  keyboard
     characters on a command line.

     Pointing Device.

     If the terminal has a pointing device, then the POD  boolean
     is  present in the _M_F_B_C_A_P entry.  If the pointing device has
     buttons, then the PDB boolean is set, the number of  buttons
     is  given  by  the  NPB  numeric  capability, and the values
     returned by the respective buttons of  the  pointing  device
     are defined by the BU1 through BU12 numeric capabilities.

     The graphics pointing device is  initialized  with  the  PDS
     format string.  The PDR 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 PDF format
     string.  The graphic pointing device is uninitialized by the
     PDE format string.

     If the PRI boolean is set, one character is read immediately
     after  the  pointing  device initialization sequence PDS and
     before the pointing device is enabled by PDR.  This is  use-
     ful  for  terminals  that  have  a  cursor  and can read its
     current position but do not have the capability of a graphic
     event  (  _i._e., an x,y pixel coordinate that is read immedi-
     ately after a key or button is pushed on the terminal).

     The pointing device encoding format string PDF  must  assume
     that  the pointing device will send one signature character.
     After the pointing is activated by the  PDR  format  string,
     the  first  character  transmitted from the terminal must be
     identical to the first character of the PDF  format  string.
     If  the  characters do not match, then the _M_F_B_D_e_c_o_d_e routine
     used by _m_f_b(_3) will return  the  first  character  that  was
     transmitted by the terminal.

     The PRBON string capability defines the  character  sequence
     to  enable rubber banding of the pointing device, and PRBOFF
     disables the rubber banding. _M_F_B_C_A_P assumes that the  center
     of  rubber banding is the current graphics position that can
     be defined by the MPS format string defined above.

     Special Modes

     If the graphics device is to be handled as a TTY,  then  the
     TTY  boolean  must  be  present in the _M_F_B_C_A_P entry.  If the
     graphics encoding can produce 8  bit,  nonASCII  characters,
     then the 8BB boolean must be included.  If the graphics dev-
     ice is a TTY and is to be driven in a _R_A_W mode, then the RAW
     boolean  must be included.  See the manual for _t_t_y(_4). Typi-
     cally, this mode is used only if the device has no keyboard.




                                                               13






MFBCAP(5)                                                 6/21/83



     _M_F_B_C_A_P 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 ALUJAM, ALUOR,
     ALUEOR, and ALUNOR respectively.

     Similar Terminals

     If there are two very similar terminals, one can be  defined
     as  being  like  the other but with certain exceptions.  The
     string capability MCE is given with the name of the  similar
     terminal.   The  MCE  must be the last capability defined in
     the entry, and the combined length of the two  entries  must
     not  exceed  4096 characters.  Because _m_f_b routines scan the
     entry from left to right,  and  because  the  MCE  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  dif-
     ferent peripherals.


FILES
     ~cad/lib/mfbcap         file  containing  terminal  descrip-
     tions

SEE ALSO
     termcap(5), mfb(3), kic(CAD1)

AUTHOR
     Giles Billingsley

BUGS
     The total length of a single entry (excluding  only  escaped
     new lines) may not exceed 8192.

     There is a restriction that allows a  simple  parser  to  be
     used  for the _M_F_B_C_A_P file.  The delimiter is assumed to be a
     comma that is not immediately preceded by a slash (\)  char-
     acter.   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.

     Not all programs support all  entries.   There  are  entries
     that may not be used by any program.









14