|
On 7/1/13 3:24 PM, Rory Hewitt wrote:
Be aware that, as pointed out above, some of those codes < x'40' arescreens
treated as 51250 data-stream control codes. Including them in your
can cause the application to crash.use a
If you want to try it out (of course you do!), try displaying x'1D' -
hex editor to add it to e.g. a record in a source file and then useSEU...
Don't say I didn't warn you...
The range from x'20' through x'3F' is screen attributes.
x'1C' is an asterisk-with-overscore, produced by the "Duplicate" key on
a 5250 keyboard.
If I had the slightest idea how to directly access the "semigraphics"
characters availible on InfoWindow II terminals, for use with
mouse-aware display files, I'd probably be using them, and the emulator
I wrote would almost certainly support them, and support mouse-aware
display files much better than it does.
--
JHHL
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.