Really?  That's really surprising; SketchMorph is just a dumb data
object, a painting, making a copy of it via the UI is a valid
use-case.  For every other kind of Morph, the green halo makes a deep
copy, SketchMorph is inconsistent, shouldn't Etoys simply override
that halo to call its own #semiDeepCopy to suit its own purposes?

Is Etoys running in trunk?  It is not targeted for trunk though, is it?

I want to be able to make easy copies of SketchMorph's.  Surely we can
come up with some solution; what about Karl's suggestion?   I think
Shift should be the sharing, because the "modifer" keys are used to
"modify" the standard behavior, which is a true veryDeepCopy..


On Fri, Apr 1, 2016 at 8:45 AM, Bert Freudenberg <bert at freudenbergs.de> wrote:
> On 01.04.2016, at 01:41, Chris Muller <asqueaker at gmail.com> wrote:
>>
>> Okay, that's why this is in the Inbox.  I started to formulate my
>> question in long words in email, but decided this was the quickest and
>> easiest way to ask it.  :)
>>
>> Okay, so this is definitely not the place to fix my problem.  So I
>> will instead try putting something into SketchMorph's veryDeepFixup:
>> which will ensure its underlying form gets copied when I green-halo a
>> SketchMorph.  SketchMorph is an exception because he's a dumb data
>> object, not a "player" who wants to share a costume.
>
> SketchMorph is the single most-used user object in Etoys :)
>
>> -- I was working on an icon, writing scripts to change colors
>> pixel-by-pixel, goofed up my "backup" SketchMorph I had torn off the
>> green halo, only to find I corrupted my original, as well.  Some work
>> lost.
>
> I’m sorry you lost time. Nevertheless, the originalForm in SketchMorph is designed to be shared.
>
> - Bert -
>
>
>
>