[Seaside] Crashing Seaside Image = Lost Work?
lochan94 at gmail.com
Wed Apr 9 05:43:02 UTC 2008
One of the reasons why your image hung would be that you have
WAComponent subclass: #XYMainView
XYView >> children
^ Array with: child
XYMainView >> initialize
child := XYChildVIew new.
XYMainView subclass: #XYChildView
XYChildView >> initialize
editor := OrderedCollection new. "or any similar statement"
The problem with the above code is, when XYMainView is initialized, child
variable is assigned a new instance of XYChildView, which also initializes.
Since XYChildView is a subclass of XYMainView, there is an infinite loop of
instantiation and thats why the image hangs.
Hope this helps,
On Wed, Apr 9, 2008 at 3:35 AM, aditya siram <aditya.siram at gmail.com> wrote:
> Hi all,
> Due to careless programming I have crashed my Seaside One-Click image
> twice today. None of my mouse and keyboard clicks work but when I 'x' out
> the window I get a confirmation dialog asking if Squeak should quit without
> saving (which I accept since I don't really have a choice). When I open the
> image all my work during the previous session is lost. Am I doing something
> wrong? Is it actually saved somewhere I don't know about?
> seaside mailing list
> seaside at lists.squeakfoundation.org
+91 9243468076 (Bangalore)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the seaside