🚀 go-pugleaf

jimm@amiga.UUCP (Jim Mackraz) writes:
>In article <3770@crash.cts.com> billk@pnet01.cts.com (Bill W. Kelly) writes:
>)ewhac@well.UUCP (Leo 'Bols Ewhac' Schwab) writes:
>
>)>>FixReq solves this problem by patching AutoRequest() to substitute
>)>>IntuitionBase->ib_ActiveWindow in place of whatever window pointer was passed
>)>>to AutoRequest().
>
>)>	JimM will probably toast you for this.
>
>)Oh, come on.  First of all, AutoRequest() (or: BuildSysRequest()) doesn't
>)put up a requester in the _window_ you give it, but in the windows' screen!
>)Now, the screen could be closed while the AutoRequest() is being displayed
>)on it, but it hasn't happened in the eighteen months I've been using it.
>
>A Toast:
>    Here's to all Empirical Programmers; may their work never inhabit my disks.

Oh, clr.l $4.
 
>Eighteen whole months.  That proves it, eh?  Where did you say you worked?

I work at Bonehead Research.  Why do you ask?
 
>Note that if the window is closed, window->WScreen is a technique we
>call "Indirection through Free Memory."  Bryce has a little program, memmung,
>that you ought to try.

Yes I know that, I know that.  

I don't suppose I'm allowed to put Forbid()/Permit() around the section of
code that gets ib_ActiveWindow and calls AutoRequest(), am I?   

Is there a "proper" way to do what I'm doing?  

(If there is, I'll change FixReq.  If not, I will continue to use the current
version of FixReq.  You may continue to be pestered by programs that don't 
bother to set pr_WindowPtr.  Have a nice day.)

--
Bill W. Kelly                                         billk@pnet01.cts.com
{nosc ucsd hplabs!hp-sdd}!crash!pnet01!billk   crash!pnet01!billk@nosc.mil