- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have a graphics program that also generatesPRINT statements, and accepts input via READ statements.
I sometimes get this "severe error" in Unit 4. It doesn't like the input from the READ * statement. This is entirely RANDOM. Sometimes it accepts it, sometimes it doesn't. Even with the exact same input characters the error occurs randomly. I am not putting in any unusual characters, just numerical digits, periods, plus and minus signs.
READ and PRINT statements don't belong in the same window as graphics output anyway. Isn't there a way to ISOLATE those from the graphics? None of these problems occur in a console application.
An intelligent system programmer should provide for that.
Don't they TEST this stuff ????
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
That's exactly what I need - a way to open a window so that CONIN$ comes from just that, and CONOUT$ goes to just that, so that READ and PRINT statements are isolated from the graphics I/O.
Is there an article I can read where this is discussed in more detail? I don't find that just the listings of the subroutine usages are that useful, it's so fragmented.
Thanks; Bill S.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page