Re: Serialization of BorderedMorph

Stéphane Rollandin <[email protected]>
Newsgroups gmane.comp.lang.smalltalk.squeak.general
Message-ID <[email protected]>
> 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]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.