Yes, that's exactly the diagnosis that I'd reached.

I don't know that I want to eliminate that code, particularly. I just
want to not have my nice background disappear because MorphicProject
>> #initialize changed. I'm stating the user story, if you like,
without suggesting a particular solution (because I know very little
about this code).

frank

On 11 September 2013 19:31, Bob Arning <arning315 at comcast.net> wrote:
> The problem is that MorphicProject class>>initialize was modified and when
> that happens, it is automatically run after loading. This method does:
>
>     Project current isMorphic ifTrue:[
>         "Set the default background in the current world"
>         Project current world color: self defaultFill.
>     ].
>
> and that's where it happened. My guess is you just want to eliminate that
> code.
>
> Cheers,
> Bob
>
>
> On 9/11/13 2:14 PM, Frank Shearar wrote:
>
> Right, so that'll be any MorphicProject update, so Morphic-dtl.668
> would cause it.
>
> Sigh. That kind've means that someone wanting to be kind would need to
> specifically preserve the background through a preamble/postscript
> pair, wouldn't it?
>
> frank
>
> On 11 September 2013 19:09, Bob Arning <arning315 at comcast.net> wrote:
>
> PasteUpMorph(Morph)>>color:
> MorphicProject class>>initialize
> MCMethodDefinition>>postload
> MCMethodDefinition(MCDefinition)>>postloadOver:
> [] in [] in [] in [] in MCPackageLoader>>basicLoad
>
> Cheers,
> Bob
>
> On 9/11/13 1:35 PM, Frank Shearar wrote:
>
> I just updated an image from 12641, and the blurry Ulam Spiral
> background disappeared, replaced by the old brushed metal background.
> What did that? Why?
>
> frank
>
>
>
>
>
>
>
>
>
>
>