🚀 go-pugleaf

In article <5143@june.cs.washington.edu>, rling@june.cs.washington.edu (Robert Ling) writes:
> In article <478@mks.UUCP>, wheels@mks.UUCP (Gerry Wheeler) writes:
> > In article <8806151250.AA29397@ucbvax.Berkeley.EDU>, U211510@HNYKUN11.BITNET (Wil Groenen) writes:
> > > I have a problem [...] reading a character from screen at current
> > > cursor position.
> > [...Entire article deleted]
> [...]
> in fixed positions.  If you also had access to the font used, the problem
> is one of (bit) pattern matching.  In high resolution, a screen character
> [... Portion of article deleted]
> 
> - Robert Ling   <rling@june.cs.washington.edu>

	Another way to do it (not reading the character bit maps after on the
screen) would be to take over the character output routines (I don't recall
what this would take), and put all the characters into an array. Of course,
if your program was the only thing generating character output, it'd be more
efficient to just put the characters in the array immediately. I would think
that you'd have to handle the VT-52 stuff that the ST does in order to get an
accurate array...

	This entire approach would only be valid if the characters in question
had not yet been drawn on the screen.


	Jason
"Not your average iconoclast"