Graphics calls dont work (?) #2

[WSinc]

Hi;

I tried isolating the problem by just having the OPEN statements by themselves.

This time, it worked, I got a child window. So then I started adding all the routines I had from the previous project. I did not change a single line of code -It STILLworked ! ! Apparently it had something to do with the build/link process. Would bringing routines from a non-graphics project have any bearing on this?

I could not get the error message back again. So the only way to isolate the problem is to send the ORIGINAL project, but I don't know how to do that in one attachment.

I am still wondering: How do I make sure that READ andPRINT statements are in the original PARENT window, and don't appear in the CHILD windows? I could not figure out which unit number (if any) corresponds to the PARENT window. So I can't use SET FOCUS (or SET ACTIVE?). It seems awkward, however to have to keep switching back and forth when you want to insert DEBUG statements, or have inputs to your program. Like I mentioned previously, console I/O should be isolated from the graphics.

BTW, when the console stuff scrolls, it causes glitches in the graphics output. Another reason they must be isolated.

Apparently PRINT and READ statements go to the newly opened graphic window unless you do something to re-route them. But not knowing what UNIT number to use, how would we do that?

We desperately need a well thought out document that covers a logical orderly step by step procedure for designing one's own graphic application. Everything is so fragmented now, it's difficult to extract information. That's why you get all these silly questions.