🚀 go-pugleaf

For a class project I am trying to modify TDS to accept Hercules graphic 
commands.  I am doing this by modifying the cserver.  In the function
DoTermPChan,  contained in itermp.c, I defined my own protocol bytes
and execute graphic functions at that point.  The problem that I am
having is that when I call the functions from the Occam side, the only
response that I get is beeps.

  For debugging purposes I have the PC side write out the command byte
read in.  I use printf("command is : %d\n", Command) before the large
switch statement. I have also created the following Occam code.


#USE userhdr
VAL tt.grph.pix.set IS BYTE 33:
INT key:
SEQ
  keyboard ? key
  IF
    (key = 'a' (INT) )
      screen ! tt.out.byte
    TRUE
      SKIP
  screen ! tt.grph.pix.set; tt.grph.pix.set
  keyboard ? key

If I input an 'a' I get the following output:

  command is: 18
  !command is: 13

If I input a ' ' I get :
  command is 13
  command is 13

'!' is ascii for 33.  18 is the protocol byte for tt.out.byte.  13 is the 
protocol byte for tt.beep.

My understanding of this is that Occam is screening output to screen, only 
allowing its protocol bytes across.  Is that right?

Any help or tips would be greatly appreciated.  Please reply to
joe@umbc5.umbc.edu.


I am running a B004 card and TDS release 4.

                                         Thanks much,
                                         Joe


----------------------------------------------------------------------------
Joseph Poole                        Student Consultant / Graduate Assistant
                                    University of Maryland Baltimore County

internet         joe@umbc5.umbc.edu
UUCP             ..!uunet!umbc5.umbc.edu!joe
bitnet           joe@umbc2



----------------------------------------------------------------------------
Joseph Poole                        Student Consultant / Graduate Assistant