#comm/vt100/printscreen
05-Jul-88 15:16:04
Sb: #133305-#comm/vt100/printscreen
Fm: Don Curtis/SYSOP 76703,4321
To: Ben Blish 72667,1341
This message turned up in search, but its forum couldn’t be identified from the original transcript, so it may not be linked into its thread.
Ben,
Ok…my idea of a 'print screen' (vs. dump screen) is a straight text
dump. Whatever text is there is dumped, everything else is ignored.
That way, you could have an 80×24 text array in memory. Everytime an
ASCII character was printed to a window or screen, it would also be placed in
that screen's text array in the proper position. Well…maybe we'd have to
define a 132×50 line array for overscan…but I think you get the idea.
If window 1 overlays window 2 on the same screen, the text from window
1 would overlay the current text from window 2. The only thing I see 'hard'
about this is the smart-refresh. I'm not sure if the Intuition routines for
doing that call text() or not.
Don