Hi Ned,

I do not think a preference is justified for this. It unnessecarily 
adds to the clutter of preferences we already have. AFAICT this only 
matters for trails on the World, which is a rarely used feature IMHO. 
So backwards compatibility should not be a problem.

-- Bert

Am Freitag, 04.07.03 um 19:40 Uhr schrieb ned at bike-nomad.com:

> from preamble:
>
> "Change Set:		ColorSeesTurtleTrailsToo-nk
> Date:			4 July 2003
> Author:			Ned Konz
>
> This adds a per-Project Preference called #colorSeesTurtleTrailsToo.
>
> When this preference is set, the #color:sees: and #touchesColor: (but
> not the #colorUnder) methods will take into account the turtle trails 
> as
> well.
>
> This makes it possible to write eToys scripts that can see the turtle
> trails.
>
> By default, this preference is false, for backwards compatibility.
>
> This also avoids an unnecessary ColorPatchCanvas copy that was in
> #patchAt:without:andNothingAbove:
>
> "
>
> Preferences preferenceAt: #colorSeesTurtleTrailsToo
> ifAbsent: [ Preferences
> 	addPreference: #colorSeesTurtleTrailsToo
> 	categories: #(scripting)
> 	default: false
> 	balloonHelp: 'if true, the ''color:sees:'' and ''touchesColor:'' tests
> in eToys (but not ''colorUnder'') will also see turtle trails'
> 	projectLocal: true
> 	changeInformee: nil
> 	changeSelector: nil
> ].!
> <ColorSeesTurtleTrailsToo-nk.cs.gz>
>