Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!lll-crg!rutgers!brl-adm!brl-smoke!gwyn From: gwyn@brl-smoke.ARPA (Doug Gwyn ) Newsgroups: comp.sys.att,comp.terminals Subject: Re: Test for status of a pixel on DMD terminal. Message-ID: <5466@brl-smoke.ARPA> Date: Tue, 16-Dec-86 11:13:27 EST Article-I.D.: brl-smok.5466 Posted: Tue Dec 16 11:13:27 1986 Date-Received: Wed, 17-Dec-86 18:54:46 EST References: <182@olamb.UUCP> Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB)) Organization: Ballistic Research Lab (BRL), APG, MD. Lines: 16 Xref: mnetor comp.sys.att:77 comp.terminals:90 In article <182@olamb.UUCP> kimcm@olamb.UUCP (Kim Chr. Madsen) writes: >Is there a way of telling whether a pixel is set or not, on the >the AT&T 5620 Terminal (aka DMD & Blit) ? There isn't any standard function that I know of, probably due to this being a fairly rare need. A simple kludge that will suffice is to clear a scratch word then bitblt() the point into it, followed by testing the scratch word for nonzero. >Is there something wrong with , since when I include it - my >program won't run and I have to make do without the routines needing the >header file to be included - Making I/O to the UNIX host a pain in the a**! works okay here. You didn't supply enough information to permit remote debugging.