RE: "Save Project on File" "almost hangs" Squeak?

Folks,

I'm a long-time lurker, building a product prototype in squeak, and I'm having a similar problem with "Save Project On A File..."

Essentially, twice now when I save my project after some changes (small project, minor changes), the change goes on forever... I see the "Publishing (collecting resources)" and the grid stay there forever. Since this is a 3.6 image (or for other reasons) the instructions that Ned sent out don't apply.

Here are the steps: 1. In the project, I select "Save Project On A File..." 2. In the "Publish This Project" morph, I choose my folder from the list, then press "Save" 3. Squeak asks "Would you like to include all the changes in the change set as part of this publishing operation?" and I select "Yes" 4. Squeak asks "Some blocks which reference instance variables are included in this segment, These may fail when the segment is loaded if the class has been reshaped. What would you like to do?" I select "keep going"

Menus work, so when I "previous project", then I get "MessageNotUnderstood: CompiledMethod>>position", abandon that and I can continue. But never save the project.

Can anyone offer some help / suggestions on what to do next? I can work around, i.e. copy code into a working instance, but I'd like to help eradicate the bug.

I can get email the image or other - suggestions welcome.

Thanks, Steve Sanderson

-----Original Message----- From: squeak-dev-bounces@lists.squeakfoundation.org [mailto:squeak-dev-bounces@lists.squeakfoundation.org]On Behalf Of Milan Zimmermann Sent: Monday, July 12, 2004 8:42 AM To: squeak-dev@lists.squeakfoundation.org Subject: Re: "Save Project on File" "almost hangs" Squeak?

Ned,

(sorry i sent this to you instead to list last night .. just a copy here, with one note/question - when playing with your solution last night I thought the "reason" why the save hang was the "improperly renamed class ZTime" - do you think it was that or just the fact I had the Changeset browser opened in the project, which made the object graph too big and Squeak decided to stop the save?)

Thanks for the detail description and help. I am now able to "save the project to file" and understand (partly) why Save did not work before, a few notes inline below:

On July 11, 2004 12:42 pm, Ned Konz wrote:

On Sunday 11 July 2004 8:22 am, Milan Zimmermann wrote:

<<snip>>

Just do this after the save failure:

• click on the desktop in the project (the copy of the one that you're

saving) that is displaying the progress morph forever (this project is called Unnamed#).

Just a note, I was only able to get control back from the "temp project" after Alt-. + Abandon.

• go to the previous project (the one you're trying to save).

I did

• click on the "OK" button on the requestor in the upper left hand corner

that says "extra associations"

Interesting - I have not seen anything in the upper left corner of my original project ...

• Open a Project history morph from the Objects tool

I did

• drag out project view morphs for any projects you didn't make yourself

(like the "Unnamed#" one you just left)

• hold the button down on each one of these and choose "expunge project"
• close the change sorter in your original project and try again.

I did

After that, I did "save" - from World menu, probably not needed - and was able to "Save Project On File" , great, Thanks!

I tried to look for the "ZTime" class in Browser before I closed the "Change Sorter" but did not find it, not sure why. In any case, do you think I must have renamed it or something else could have happened to the image? - Just curious, I am not aware of renaming any class, perhaps by accident .. I have been playing with creating classes from the workspace, perhaps I messed up at some point.

Thanks for your help, hope once I know more about Squeak I'd be able to fix such things :)

Milan

What's happening here is this:

• You ask to save the project.

• Squeak creates a new project that is a copy of the one being saved, and

changes into it. This is the one that shows the progress morph and the grid.

• It finds something that it doesn't want to save (see below). This more

or

less aborts the saving, but instead of cleaning up the temp project and changing back to your original project, you're left in the temp project. Which actually isn't saving any more, despite the progress morph being displayed.

• You will find that in the temp project the menu works as soon as this

happens (when it changes from "collecting resources" and starts displaying numbers again). Go to the previous (parent) project; this will be your original.

• In the original project, there is at the upper left hand corner of the

world a string informer saying "extra associations". This means (to the three or four people who know and remember this) that "something bad happened and your project didn't get saved correctly."

• The cause of this was an improperly renamed class called "ZTime" which

is

being held in the change records of a change set which is being held by

the

ChangeSorter that you have in your project.

I'm looking into how we could better handle this kind of thing.