[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: memory checking function
- To: "Dave Wroblewski" <davew@atqm.advtech.uswest.com>
- Subject: Re: memory checking function
- From: cfry@MIT.EDU (Christopher Fry)
- Date: Wed, 25 Nov 92 16:30:45 EST
- Cc: info-mcl@cambridge.apple.com
> Date: 25 Nov 1992 11:34:36 U
> From: "Dave Wroblewski" <davew@atqm.advtech.uswest.com>
> Subject: Re: memory checking function
> To: info-mcl@cambridge.apple.com
>
> Reply to: RE>memory checking function
> >> MCL has two undocumented hooks for the GC....
>
> This message reminded me that I occasionally want to disable the cursor
> switch to "GC" that accompanies a GC (especially during demos -- I
> don't care if a GC happens, I just don't want to have to explain the
> cursor to someone)
>
> Is this implemented using these hooks? If not, is there a way to disable
> this feature? If not, could one be installed in upcoming patches/versions of
> MCL?
I second this feature request. What would be nice is a way for
us hackers to know that GC is happening without bothering the
casual user. Maybe a dot or small font "g" in the menu bar?
Would replacing the GC cursor with a watch cursor be sufficient?
Or how about a slightly modified watch cursor that looked like the
watch to casual observers but the eagle-eye could tell it was a gc.