Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!cornell!uw-beaver!tektronix!decvax!spray!anson From: anson@spray.CalComp.COM (Ed Anson) Newsgroups: comp.sys.mac.programmer Subject: Re: MultiFinder Weirdness Message-ID: <2449@spray.CalComp.COM> Date: 5 Oct 88 14:10:29 GMT References: <1420@ndsuvax.UUCP> Reply-To: anson@spray.UUCP (Ed Anson) Organization: CalComp, A Lockheed Company, Hudson, NH, USA Lines: 45 In article <1420@ndsuvax.UUCP> nopuklic@ndsuvax.UUCP (Blayne Puklich) writes: >In article rj0z+@andrew.cmu.edu > (Robert George Johnston, Jr.) writes: >> >>the program runs just fine, but when the >>application is first launched, the application window opens underneath >>all other open windows (such as the Finder's). > > Check your GetNewWindow() or NewWindow call, you probably are >passing NIL for the behind parameter. You need to pass WindowPtr(-1) >rather than NIL. I don't think that's the problem, for two reasons: 1. Window ordering parameters are effective only within the application's layer. Supposedly, the current application's layer is always on top. 2. I have seen the same (or similar) phenomena in commercially available software. NCSA Telnet does this to me. When it starts up, it opens a window full of information, which goes away when I first click the mouse. It opens behind the windows opened by the Finder and other applications, and then comes forward. Unfortunately, it doesn't repaint the part that was obscured, so what I see is a mostly empty window. ResEdit (v 1.1b3) does something similar. When I open a DLOG resource and double click to see the DITL info, I get a bizarre result. Windows behind the edit window show through! But only the windows from other applications! That is, ResEdit's windows stay behind it like they should. When I move the edit window, the show-through stuff moves with it. It appears as though the system isn't aware of anything out of order. If I manage to force an update of the window, everything goes back to normal. Until now, I just assumed my own copy of the system is a bit strange (It is.) But now that I see someone else with a similar problem, I think it is a bit more general. I don't have any insight into what's happening. In particular, I haven't been able to replicate the problem in my own code. Maybe someone on the net has better insight. For the record: I'm running System 6.0 on a Mac II. I'm also running several INITs, which may or may not be related to the problem. -- ===================================================================== Ed Anson, Calcomp Display Products Division, Hudson NH 03051 (603) 885-8712, anson@elrond.CalComp.COM