Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!ucsd!ucbvax!rchland.iinus1.ibm.com!dgross From: dgross@rchland.iinus1.ibm.com (Dave Gross) Newsgroups: comp.soft-sys.andrew Subject: Re: bug in proctable? Message-ID: <4bVCqbw91E6JM7W4w=@rchland.ibm.com> Date: 4 Jan 91 21:03:35 GMT References: Sender: daemon@ucbvax.BERKELEY.EDU Reply-To: Dave Gross Organization: The Internet Lines: 18 Excerpts from mail: 4-Jan-91 Re: bug in proctable? BillJanssen@RCHGATE.rch (179+0) > In general, if you are going to call frame-delete-windowthrough the > proctable mechanism, you had better call it with an instance offrame. > Was myview a subclass of frame? > Bill No, it's a subclass of view. I see the problem. Unfortunately, there's noway to get a handle on the current frame unless I keep track of it in aninstance variable. Even then, how do I pass it to the proctable entry? I seems that proctable wasn't designed to call other objects in the currentview tree, just the current object and any inherited class procs. Is thatright? -- Dave