So what basically shoud be done in Pharo is that a halt in the Morphic loop thread should behave like a haltOnce ?
On 02 Dec 2009, at 11:04, Tudor Girba wrote:
This is mainly because the UI logic is completely different. As far as I understand, in Morphic you get a loop that is dedicated for displaying the UI (much like in games user interface).
Cheers, Doru
On 2 Dec 2009, at 14:59, Johan Fabry wrote:
Hmm, OK I understand the problem. I suppose this produces the similar problem of unresponsive image if a wrong-number-of-args block is passed to Mondrian. So now the questions are:
- why can I do the same in VisualWorks without any problems?
- how can we get the same behavior in Pharo?
On 02 Dec 2009, at 10:21, Tudor Girba wrote:
Hi Johan,
I just noticed that you used "self halt" in your example.
The problem is that if you put it in the rendering code this will basically get invoked every 30 ms. A more practical solution is to use haltOnce. This is the same as halt, only that it is guarded by a global flag. Just make sure that you enable it from the Debug world menu.
Cheers, Doru
On 2 Dec 2009, at 13:10, Johan Fabry wrote:
Hi Stef, this is the same behavior as what I reported in http://code.google.com/p/pharo/issues/detail?id=1525and http://code.google.com/p/moose-technology/issues/detail?id=237 How to reproduce is also there.
-- Johan Fabry jfabry@dcc.uchile.cl - http://dcc.uchile.cl/~jfabry PLEIAD Lab - Computer Science Department (DCC) - University of Chile
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Value is always contextual."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Johan Fabry jfabry@dcc.uchile.cl - http://dcc.uchile.cl/~jfabry PLEIAD Lab - Computer Science Department (DCC) - University of Chile