[etoys-notify] [JIRA] Commented: (SQ-327) Project saving failed silently

[tracker at squeakland.org]

     [ http://tracker.immuexa.com/browse/SQ-327?page=comments#action_36543 ]
     
Scott Wallace commented on SQ-327:
----------------------------------

I've now been able to reproduce the problem reliably, basically following Korakurider's formula.  My experience may provide useful clues:

In a blank project, bring up the Guides, navigate to "Script Tiles" -> "Hide and Show".

Select the "Script Tile Hide and Show" book with the halo, and tear off a duplicate using the green halo handle; drop the duplicate on the world.

In a workspace evaluate "(ScriptEditorMorph allInstances select: [:m | (m instVarNamed: #firstTileRow) = 2]) select: [:m | m submorphs size < 2]" and notice that there are no such malformed morphs.

Click on the "Help" tab to close the flap.  It's important that it not be "dismissed" by clicking on the ? in the toolbar at this point; just click on the tab.

Evaluate the above expression again -- still no malformed morphs.

Save the project to disk -- it works fine; doesn't hang.

Now, the surprising thing:  Click on the "?" in the toolbar, so that the entire quick-guides flap and tab vanish.  This will now leave the project in a state in which the saving will fail.

But before saving again, after dismissing the quick-guides evaluate the expression again -- aha! suddenly there are ScriptEditorMorphs exhibiting the malfunction -- notice BTW that this is not an "inverted scriptor tile" situation, it's a case where there's a ScriptEditorMorph that claims to have a header (firstTileRow = 2) but which in fact has *no* submorphs.  Moreover, I observe that the "playerScripted" of a typical such faulty ScriptEditorMorphs is an instance of an *obsolete* uniclass.

So somehow dismissing the Guides has resulted in the presence of problematical ScriptEditorMorphs, whereas when the Guides were present, there were no such problems.  It seems that the housecleaning done when removing the QuickGuides from the system, particularly BookMorph>>deleteAlongWithPlayers, is removing uniclasses that are still needed by content in the duplicated book which outlives the copy of the Guide from whence it was duplicated.  When/if this happens, I wonder whether such a dependency, if it occurred, would actually always be an "error" -- depends perhaps on some unarticulated aspects of the semantics of "duplication" of books.  In any case, it does appear that there are uniclasses referenced in the duplicate which have gotten clobbered when the Guides got removed.

This may therefore point to a deeper problem in the duplicating of books...  or perhaps just of ScriptEditorMorphs.

Anyway, after you've dismissed the Guides, your project will be in the state where "saving" it will hang.  When the hanging takes place, choose "previous project" from the world menu to get to the temporary project in which the error notifier can be seen.

[Finally... I apologize for speculating that SISS might have been at fault :-)  Clearly that's not the case!]

> Project saving failed silently
> ------------------------------
>
>          Key: SQ-327
>          URL: http://tracker.immuexa.com/browse/SQ-327
>      Project: squeakland
>         Type: Bug
>   Components: etoys
>     Reporter: korakurider
>  Attachments: SqueakDebug.log
>
>
> This was observed in Etoys-to-Go 2253 on WindowsXP(I haven't to try to reproduce it with other)
> 1) Create and enter new project
> 2 Open "Script Tile"->"Hide and Show" of QuickGuides
> 3) Duplicate Book of the guide and paste into the new project
> 4) Try to save the project,
>   then saving faild and debug.log is created.  
>   The failing itself is bad, but worse thing is that Etoys keeps showing "Mesh Screen" and doesn't show any error message, it just failed silently.
> I can save other project ofcourse.
> Debug log is attached.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://tracker.immuexa.com/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira