mwilkins@jarthur.Claremont.EDU (Mark Wilkins) (03/28/90)
In a piece of code I'm writing, I call NewWindow with perfectly conventional, initialized parameters. Under most conditions it works perfectly, but under a few easily reproducible conditions it will take the boundsRect being put in and change it to apparently random values, causing the window to fail to appear. There is no out of memory error occurring , because those are being trapped, and the return value is otherwise good. First, I am not running any of my own inits which might patch NewWindow, nor am I using any unusual WDEFs. The machine's a IIci, running System 6.0.5 and MultiFinder. I KNOW that NewWindow is changing the value of the boundsRect parameter because the _NewWindow trap is where the change occurs while tracing through with a machine-level debugger. Is there any way that NewWindow is supposed to change the value of its boundsRect parameter? Why is this happening? What could I be doing wrong? Or are my ROMs buggy? :-) -- Mark Wilkins mwilkins@jarthur.claremont.edu