TIP: Click on subject to list as thread! ANSI
echo: cis.os9.6809.coco
to: Kevin Darling, 76703,4227 (X)
from: Brother Jeremy, CSJW 76477,142
date: 1991-09-11 22:13:13
subject: #Lines/Put/etc

#: 12194 S10/OS9/6809 (CoCo)
    11-Sep-91  22:13:13
Sb: #Lines/Put/etc
Fm: Brother Jeremy, CSJW 76477,142
To: Kevin Darling, 76703,4227 (X)

Dear Kevin

Based on advice which you gave to George Hendrickson in MSG 9952, I tried the
following code:

PROCEDURE TestNewLine

(* usage: RUN NewLine(path,a,b,c,d)

DIM path,a,b,c,d:INTEGER

path=1

RUN gfx2("CLEAR")

RUN NewLine(path,10,25,10,75)


PROCEDURE NewLine

(* usage: RUN New(path,etc)

Param path,a,b,c,d:INTEGER

DIM esc(10):BYTE

esc(1)=$1B

esc(2)=$44

esc(3)=a/256

esc(4)=land(a,$FF)

esc(5)=b/256

esc(6)=land(b,$FF)

esc(7)=c/256

esc(8)=land(c,$FF)

esc(9)=d/256

esc(10)=land(d,$FF)

PUT #path,esc

It worked, sort of. Instead of getting a staight line, I got a diagonal. I
figured out that the calling program had to have all the values in hex. When I
changed it, the program worked. Is there any way around this. I would like to
be able to call NewLine with the same parameters as I would in calling the gfx2
Line command. Is there a short piece of code which could convert the decimal to
hex prior to being processed by newline?

This is all still sort of new to me, so please forgive my asking what should be
obvious.

As ever, Br. Jeremy, CSJW



There is 1 Reply.

SOURCE: compuserve via textfiles.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.