[FIX] Colors and connection dialog (Version 2)
arning at charm.net
Mon Nov 20 19:40:34 UTC 2000
On Mon, 20 Nov 2000 14:32:06 -0500 Geoffrey Corey <gcorey at redsky.com> wrote:
>Never noticed the block method fixTemps. It does
>correct the problem. Is this method specific to squeak?
I suspect it is. Since BlockContexts are not true closures yet, and due to some (IMHO) iffy assumptions about reuse of contexts that may differ between debugged code and pure VM interpretation, method temps are not 100% reliable in cases like the one below. The use of #fixTemps often helps get one closer to the expected results.
>I don't ever
>recalling having to use this when I did VisualWorks years ago.
>From: Bob Arning [mailto:arning at charm.net]
>Sent: Monday, November 20, 2000 2:05 PM
>To: squeak at cs.uiuc.edu
>Subject: Re: [FIX] Colors and connection dialog (Version 2)
>On Mon, 20 Nov 2000 13:51:09 -0500 Geoffrey Corey <gcorey at redsky.com> wrote:
>>The problem with the
>>original class was the local variables being used in openConnectionDialogue
>>were being garbage collected under NT and Macinstosh. Why? I'm not sure.
>>My theory is the local variables are copied under UNIX via process fork
>>(dialog openInView) and not under NT or Mac (no concept of process fork).
>I wonder if the following change in #openConnectionDialogue will also fix
> connectButton _ PluggableButtonMorph
> on: [
> textEntryList do: [ :m | m hasUnacceptedEdits
>ifTrue:[ m accept ] ].
> self connect
> ] fixTemps
> getState: nil
> action: #value.
More information about the Squeak-dev