Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!pepper!cmcmanis
From: cmcmanis%pepper@Sun.COM (Chuck McManis)
Newsgroups: comp.sys.amiga
Subject: Re: Burning Questions
Message-ID: <35324@sun.uucp>
Date: Wed, 2-Dec-87 13:38:38 EST
Article-I.D.: sun.35324
Posted: Wed Dec  2 13:38:38 1987
Date-Received: Sat, 5-Dec-87 16:59:33 EST
References: <6570001@hpindda.HP.COM> <6570004@hpindda.HP.COM>
Sender: news@sun.uucp
Reply-To: cmcmanis@sun.UUCP (Chuck McManis)
Organization: Sun Microsystems, Mountain View
Lines: 53

In article <6570004@hpindda.HP.COM> (Grant Haidinyak) writes:
>Also, I had a WindowToFront(win_main) before the get_log() call, but
>when I took the call out, the requestor appeared when specified.
>(win_main was already to the front of the window stack).

Is your window a SIMPLE_REFRESH window? I recently noticed that when you
move a SIMPLE_REFRESH window to the front of the list it gets cleared to
0 for some reason (But you get a refresh request to redraw it). Also you
should know that the WindowToFront() operation happens asynchronously. That
is, you call WindowToFront() and it returns, then sometime later your 
window actually gets moved to the front. There are two ways I can think of
off the top of my head to determine when your window has made it to the 
front. One is to spin on (window->WScreen->FirstWindow == window) the
other is to wait for the REFRESHWINDOW message and assume that it meant you
are now in front. 

>What I mean by double click, is click on the left (select) button twice.

I thought of something else that could cause this behaviour, that is 
if you had REQVERIFY set, but you don't mention it so I assume you don't.

>I'm not opening an initial window, I'm just opening a standard port.
>Also, the setup described above, is correct. However, closing the window
>isn't how it is described in the "Intuition" manual (which could now be
>out of date, as I have the original manuals).  In the manual, to close a
>window with a shared message port, it says to NULL out the message port
>field in the window structure, but to leave the IDCMP field alone.

The manual is correct, I was wrong, you don't NULL out the IDCMP flags.
You may still get messages from this 'closed' window if you plan it 
right :-). Since Intuition queues messages until you can get to them. 
In my code I check to see if the 'other' window pointer is now NULL, and
if it is just throw away messages coming from it. 

>Would you or anyone else please post, or tell me where to get the
>CloseWindowSafely() routine.  (I want to do things "right", not just do them)

If I can find a copy of it I will post it.

>Also, since I'm on my soapbox, how do I get the Autodocs that are refered
>to by the Enhancer Manual.

Write "I want the Native Developers Update, here is $20 and my address ..."
on a sheet of paper put it into an envelope and mail it to :
	Lauren Brown
	CATS
	1200 Wilson Dr.
	West Chester, PA 19380


--Chuck McManis
uucp: {anywhere}!sun!cmcmanis   BIX: cmcmanis  ARPAnet: cmcmanis@sun.com
These opinions are my own and no one elses, but you knew that didn't you.