Hello all, The answer in general is "no." The only caveat with Seaside code is that (I gues due to continuations??), it is possible to make simple mistakes with harsh consequences. My early attempts at Seaside programming were not pretty; with two books now available, it should be easier to start out knowing not to render in callbacks and vice versa. Is the Seaside code in this case poorly-behaved? Bill -----Original Message----- From: pharo-project-bounces@lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Stéphane Ducasse Sent: Tuesday, August 17, 2010 2:04 PM To: Pharo-project@lists.gforge.inria.fr; panu.suominen@iki.fi Subject: Re: [Pharo-project] Should I be able to hang my pharo 1.1 image so easily? thanks for reporting that. do you have a case that we could reproduce or have an image people could access? Stef On Aug 17, 2010, at 8:30 PM, Panu Suominen wrote:
I think I have the same problem. It does not actually jam the image right away but makes it really slow which renders it unusable. After a while memory runs out and it crashes. Have not seen this many times thou. It would help if there was a key sequence which would suspend other than UI process.
-- Panu
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project