;
;   *-*-*   RUNUTILS.CSD   *-*-*
;
;   This submit file executes the RGI Graphic Utility sample programs.
;
;   This submit file should be run after you have used gen386.csd to
;   generate the RGI utilities.  inutil386.csd can be run to install the
;   utilities in the /util386 directory if desired.
;
;   The sample programs are divided into groups.  Each group is separated by
;   the *-*-* line and all commands beteen lines should be executed together.
;
;   What follows is commented out so the novice user doesn't get
;   in trouble.  Uncomment each line after you figure out what it
;   does.  Most of the boards capabilities are explored.  Before
;   proceeding you should have mastered installation, configuration,
;   and use of terminals with login and aedit - in fact you should
;   be reading this file in an iSBX 279A terminal window to qualify as
;   an advanced beginner.  The information in the remainder of this file,
;   if studied and understood should bring you to intermediate level.
;   Actually using the example code to create a useful application
;   will do the rest.
;
;*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
;
;   Graphics windows must be attached as physical devices.
;   The following aliases will replace any user-added aliases named
;   adv and ddv.  These are also standard aliases in :prog:alias.csd.
;
;
alias adv=attachdevice g279_0 as :vdi: physical
alias ddv=detachdevice :vdi: force
;
;*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
;
;   A little demo:  bltit.
;   bltit uses windows, metafiles, bitmaps, and raster-ops.
;
;adv
;bltit
;ddv
;
;*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
;
;   This is an automated version of the old number puzzle game named bmapper.
;   bmapper has never won this game.
;
;adv
;bmapper -p 255 -i 4 -w 160 -g 0 -m rose4.met -n 200
;ddv
;
;*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
;
;   Neither of the above programs expect the background metafiles to
;   perform window or bitmap manipulations.  Feeding them metafiles
;   that perform these operations will produce unpredictable results.
;   ARCPLAY.MET should not be used with these programs.
;
;   Figure out how this is drawn.  The Sleep utility provided on one of the
;   Supplemental Software disks is required to view the results.
;
;adv
;copy arcplay.met to :vdi:
;sleep 15
;ddv
;
;*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
;
;   These utilities are handy for dealing with colors.
;   Be careful of 8BPP HW Windows.
;
;adv
;showcolor -n 256
;loadcolor -r 80
;sleep 5
;loadcolor -g 80
;sleep 5
;loadcolor -b 80
;sleep 5
;loadcolor
;loadcolor -o table.h
;
;   Actually changing deftab.h customizes your default color table.
;
;loadcolor -r -g -b
;sleep 4
;
;   Which random seed that produces the most
;   visually pleasing color table?
;
;loadcolor -s 5000
;sleep 3
;loadcolor -s 500
;sleep 3
;loadcolor -s 50
;sleep 3
;loadcolor -s 5
;sleep 3
;loadcolor
;ddv
;
;*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
;
;   Some Old Metafiles with New Tricks!  The WVI on the iSBX 279 Graphical
;   Unit Information screen should be set to YES to run these samples.  The
;   default value in the Standard Definition Files has WVI set to NO.
;   Setting WVI to YES will cause a black square to appear when :vdi: is
;   detached or the system is shutdown which is why WVI is NO by default.
;
;adv
;copy intel1.met to :vdi:
;cgi -c intel1.met > intel1.c   ; New Trick
;submit cc386(intel1)
;intel1.386
;
;copy intel2.met to :vdi:
;cgi -c intel2.met > intel2.c
;submit cc386(intel2)
;intel2.386
;ddv
;
;   Note how this program preserves the primary image.
;
;adv
;copy arcplay.met to :vdi:
;mouse
;ddv
;
;   Don't bother to run cgi on rose4 unless you have a lot of disk space.
;   cgi will also take apart image files if they use integer precisions of
;   8 bits for RLE.  See gqdisplayimage.  It uses 16 bit ints.
;
;   gconvert is for importing CGM files.  Use it at your own risk.
;   Use cgi -c (or -r) after importing to get C source and then 
;   massage the code to fit your application.  ARCS, ELLIPSES, and TEXT
;   will present the most portability problems.
;
;*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
;
;   The last two examples require remote systems.  This one requires a metafile
;   to exist on the remote system. The remote system could be iRMX, XENIX or
;   UNIX.  The last example requires a remote UNIX or XENIX system.  Replace
;   anything between and including '<' and '>'  with the appropriate text.
;
;   On OpenNET, try this:
;
;offer :vdi: as vdi
;attachdevice <remote_system> as :r: r
;copy :r:<your favorite picture file name> to :vdi:
;detachdevice :r:
;
;*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
;
;   Try running mouse on a remote system.
;
;vt <remote xenix/unix>
;net use r //thisbox/super <the super-user password>
;cat //r/sd/rmx286/rgi/samples/intel1.met > //r/vdi
;
;   Any system can access any screen in this way...
;   It is possible to build interactive non-iRMX applications if the
;   data-stream generator exists on the non-iRMX host.
;   Also, terminal units behave in similar fashion, as expected.
;
; That's All!