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

> 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.

> Updating the image from trunk currently fails in MCMethodDefinition>>initializeWithClassName:classIsMeta:selector:category:imteStamp:source: with UndefinedObject>>asSymbol not understood.
> The method in question is StandardFileMenu>>advance:containingDirectoriesFrom:
>
> The
> method is defined and categorized in 'private'. When I do a
> 'implementors off ...' I get a followup error in TextMorphEditor>>setSearch: (UndefinedObject does not understand #asText). The
> result of 'model autoSelectString' is nil. I came to that through the
> method finder which actually lists 2 implementations, one in
> StandardFileMenu and one in StandardFileMenu class, but I can't find
> the one in the class, hence the implementors...
>
> Running Debian/Linux amd64 with squeak-vm 3.10-6.
>
> Does anybody know what I'm doing wrong? Or should be doing but aren't?
>
> I'm new to this so I hope I got all the information.
>
> Thanks,
> Markus
>
>
>      
>
>
> ------------------------------------------------------------------------
>
>

> Updating the image from trunk currently fails in MCMethodDefinition>>initializeWithClassName:classIsMeta:selector:category:imteStamp:source: with UndefinedObject>>asSymbol not understood.
> The method in question is StandardFileMenu>>advance:containingDirectoriesFrom:
>
> The
> method is defined and categorized in 'private'. When I do a
> 'implementors off ...' I get a followup error in TextMorphEditor>>setSearch: (UndefinedObject does not understand #asText). The
> result of 'model autoSelectString' is nil. I came to that through the
> method finder which actually lists 2 implementations, one in
> StandardFileMenu and one in StandardFileMenu class, but I can't find
> the one in the class, hence the implementors...
>
> Running Debian/Linux amd64 with squeak-vm 3.10-6.
>
> Does anybody know what I'm doing wrong? Or should be doing but aren't?
>
> I'm new to this so I hope I got all the information.
>
> Thanks,
> Markus
>
>
>      
>
> ------------------------------------------------------------------------
>
>

> 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.

> 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 <[hidden email]>
> To: The general-purpose Squeak developers list <[hidden email]
> >
> 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 -
>
>
>
>

> Now that's an interesting suggestion that had not occurred to me.  Is
> there some way we could leverage this fact to avoid this sort of  
> problem
> in the future, it seems to have come up more than once already.
>
> On the one hand perhaps the updating logic could create a new  
> temporary
> project and enter it before starting the update then exit and delete  
> it
> when the update is complete?

>
> On Thu, 2009-08-27 at 23:05 +0200, Bert Freudenberg wrote:
>> 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
>
>

> Now that's an interesting suggestion that had not occurred to me.  Is
> there some way we could leverage this fact to avoid this sort of  
> problem
> in the future, it seems to have come up more than once already.
>
> On the one hand perhaps the updating logic could create a new  
> temporary
> project and enter it before starting the update then exit and delete  
> it
> when the update is complete?

> 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 <[hidden email]>
> To: The general-purpose Squeak developers list <[hidden email]>
> 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 -
>
>
>
>

> Sorry, old age. This time with attachment ...
>
>
>
> ----- Original Message ----
> From: Markus Lampert <[hidden email]>
> To: The general-purpose Squeak developers list <[hidden email]
> >
> Sent: Thursday, August 27, 2009 4:53:17 PM
> Subject: Re: [squeak-dev] Loading morphic-ar.162 fails
>
> 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 <[hidden email]>
> To: The general-purpose Squeak developers list <[hidden email]
> >
> 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 <[hidden email]>
>> To: The general-purpose Squeak developers list <[hidden email]
>> >
>> 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 -
>>
>>
>>
>>
>
>
> <SqueakDebug.log>

> Sorry, old age. This time with attachment ...
>
>
>
> ----- Original Message ----
> From: Markus Lampert <[hidden email]>
> To: The general-purpose Squeak developers list <[hidden email]>
> Sent: Thursday, August 27, 2009 4:53:17 PM
> Subject: Re: [squeak-dev] Loading morphic-ar.162 fails
>
> 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 <[hidden email]>
> To: The general-purpose Squeak developers list <[hidden email]>
> 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 <[hidden email]>
>> To: The general-purpose Squeak developers list <[hidden email]>
>> 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 -
>>
>>
>>
>>
>
>
> <SqueakDebug.log>