[squeak-dev] Loading morphic-ar.162 fails

Markus Lampert markuslampert at yahoo.com
Thu Aug 27 23:53:17 UTC 2009


I created a new morphic project, went into it and started the upload, still chokes at the same spot, log attached.

As a side note, the text window I have open is also in a project. Both projects (the only ones in this image) were created on the main desktop (New Changes). Originally I did all the upgrades from 'New Changes'. Other than the 'Load Code Update' button I have closed and removed everything else (including the flaps) that was open in the original image.

Have fun,
Markus



----- Original Message ----
From: Bert Freudenberg <bert at freudenbergs.de>
To: The general-purpose Squeak developers list <squeak-dev at lists.squeakfoundation.org>
Sent: Thursday, August 27, 2009 2:05:48 PM
Subject: Re: [squeak-dev] Loading morphic-ar.162 fails

Simply entering a new project before updating should work as well.

- Bert -

On 27.08.2009, at 19:10, Markus Lampert wrote:

> I have indeed one text window open. I'm hesitant to close it though since I did some manual formatting in the file and would hate to have to do that again. Is there a way to maintain the formatting over saving and reading again?
> 
> Thanks for all the pointers!
> 
> Have fun,
> Markus
> 
> 
> 
> ----- Original Message ----
> From: Bert Freudenberg <bert at freudenbergs.de>
> To: The general-purpose Squeak developers list <squeak-dev at lists.squeakfoundation.org>
> Sent: Thursday, August 27, 2009 8:24:13 AM
> Subject: Re: [squeak-dev] Loading morphic-ar.162 fails
> 
> 
> On 27.08.2009, at 17:18, Danie Roux wrote:
> 
>> Markus,
>> 
>> I just updated my "2 day behind" image and it went through fine.
>> 
>> On Thu, Aug 27, 2009 at 4:40 PM, Markus Lampert wrote:
>>> When I do a 'implementors off ...' I get a followup error in TextMorphEditor>>setSearch: (UndefinedObject does not understand #asText).
>> 
>> Interestingly Morphic-ar.162 fixes exactly that. The SqueakDebug log
>> only has the stack related to the "implementors of" failure.
>> 
>> Maybe try again, and at the time Monticello fails look at the
>> SqueakDebug.log and see if the Monticello failure is in there. Then
>> send that.
> 
> 
> Maybe close the text windows you opened and update again?
> 
> - Bert -
> 
> 
> 
> 


      



More information about the Squeak-dev mailing list