In the '97 Mac Hacks is a frivilous but truly Mac-like and totaly fun thing
called Wacky Windows. It plays wacky sounds and causes windows to jump all
over the screen when they are opened, closed, updated, etc.

I have a program that uses the WINDOW OUTPUT statement at chosen low level
event processing (ON EVENT...) to update the cursor when it is over certain
regions of the main window and to update some EDIT fields. The WINDOW
OUTPUT statement is required to make sure that the output goes to the main
window and not one of several other windows that may be open and are kept
in front of the main window. The program works fine but with Wacky Windows
in force, each WINDOW OUTPUT statement causes it to do its wacky thing
which _really_ cuts down on the usability of the 2 programs together.

Is there another way to guarantee which window gets the output without
using the WINDOW OUTPUT statement and causing the Wacky side effects? A
toolbox call with some data from the WINDOW structure perhaps?

Thanks,

Charlie Dickman
charlied@...