Re: Serialization of BorderedMorph

Well, the thing is that clients load old objects through a data stream 
and expect die instVars to have an effect. We could raise and error and 
force clients to fix their code ... we want to phase-out that thing in 
BorderedMorph. The entire class is basically not needed at this point. 
Borders are available via composition, not inheritance.

Best
Marcel

Am 24.08.2026 um 10:15 schrieb Stéphane Rollandin:
>> Would a safeguard "Project current addDeferredUIMessage: [ ... ]" or "[
>> ... ] on: Error do: [:ex | ]" help for your case?
> Off the top of my head I would say no, because the culprit is the 
> arbitrary large side-effect of having a #changed sent.
>
> I think the simplest approach would be to not send #borderWidth: and 
> #borderColor: (of which we also do not know what they do for a 
> specific morph) but instead implement the specific refactoring needed 
> in BorderedMorph for backward compatibility.
>
> Best,
>
> Stef
>
>
Squeak-dev mailing list -- [email protected]
To unsubscribe send an email to [email protected]