ZZ>
  >  >> I read through VIO.DOC but could see no mention of VioSetFont...
  >
  >  JdeBP>   VIO.DOC ?
  >
  > DevCon5_disk1:/source/32text/vio.doc
ZZ>

  The 1.3 Developers' Toolkit is the primary reference for the VIO, MOU,
  and KBD APIs on Intel OS/2.  Try there.

ZZ>
  >  JdeBP> CSet/2 (which is the old 16-bit C compiler) should have it already
  >  JdeBP> For use with CSet++ (the 32-bit C/C++ compiler), you may or may
  >  JdeBP> not have to edit some headers to get the correct thunking.
  >
  > I don't think this is correct. C Set/2 is a 32 bit compiler.
ZZ>

  The headers supplied in the 1.3 Toolkit for VIO, MOU, and KBD require
  some care with thunking when accessed from 32-bit flat model code.

  The headers supplied in the 2.1 Toolkit for VIO, MOU, and KBD (#define
  INCL_SUB before #include ) will fortunately do the thunking for
  you on CSet++.  Or you could use the 32TEXT stuff from the DevCon,
  which doesn't require thunking in the headers because it is little
  more than a thunking layer itself.

  In either case, the *documentation* for VIO, MOU, and KBD on Intel
  OS/2 is in the 1.3 Toolkit.

  It's important when discussing APIs such as VIO to get your 16s and
  32s clear, otherwise you are going to be as confused as hell and your
  programs won't work.

  CSet/2 is the name of the old 16-bit C compiler, which won't need
  thunking to access the VIO, MOU, and KBD APIs from the 1.3 Toolkit.
  The name of the 32-bit C/C++ compiler is CSet++, which requires
  thunking to access those APIs.

  The box that I looked at today contained IBM's 32-bit C/C++ compiler,
  and says "CSet++" on the side.

  In large friendly letters, no less.

  It doesn't say "Don't Panic", on the front, though.

  > JdeBP <
___
 X MegaMail 2.10 #0:
--- Maximus/2 2.02