jpf10694@uxa.cso.uiuc.edu (Joseph Peter Fleck) (02/13/91)
1:If "USE THE DEBUGGER" is not checked, and I exit out of my program back to
the compiler, I get about 5 beeps and then it exits (which really makes me tend
to use the debugger as this gets very annoying very quickly) Any ideas? I've
tried flushing the events right before exit, but no help there.
2 : If my program is run from the finder, and windows are open, the open windows
on the desktop take precedence over my game which is also equally annoying.
Yes, I've made sure that the -1L is in the getCWindow line. I'm stumped there,
too. Any help will be greatly appreciated. If you could e-mail me an answer
that would be good, but a reply here is Ok too. Thanks!
-Joe
jpf10694@uxa.cso.uiuc.eduAron_Fingers_Nelson@cup.portal.com (02/15/91)
Joseph, Are you using Oncue? I seem to remember some problem with launching the Think C application from Oncue while in MultiFinder. I remember MultiFinder 6.1b9 ? Was able to solve this problem. aron_nelson@cup.portal.com
jpf10694@uxa.cso.uiuc.edu (Joseph Peter Fleck) (02/16/91)
>Are you using Oncue? I seem to remember some problem with launching the >Think C application from Oncue while in MultiFinder. I remember >MultiFinder 6.1b9 ? Was able to solve this problem. I am using MultiFinder 6.0.4. Which of the two problems did it solve? Do you mean when you launch Think C from OnCue (yes, I am using OnCue, Btw), or when you launch my application? Thanks -Joe
Aron_Fingers_Nelson@cup.portal.com (02/21/91)
Joe, I think Oncue causes the beeps to occur when launching Think C. After quitting the program ( which has been run in the integrated environment) several beeps occur. Sometimes many beeps. Sorry for the late follow up, the usenet service at Portal has been broken. aron