3 Sep
2014
3 Sep
'14
8:42 p.m.
I noticed this as well. I think that with 2 Roassal diagrams showing Pharo uses 100% CPU
time and the Shout process times-out when styling (I remember seeing some logic for that
in Shout somewhere). It would be good to address the CPU usage of Roassal in any case, and
I think it will solve the Shout problem.
On Sep 3, 2014, at 11:40 AM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote:
Oh…
That is strange. I have noticed this with Shout. If several Roassal views are open, Shout
does not work anymore. No idea why
Cheers,
Alexandre
On Aug 29, 2014, at 11:20 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote:
---> Save our in-boxes! http://emailcharter.org <---
Johan Fabry - http://pleiad.cl/~jfabry
PLEIAD lab - Computer Science Department (DCC) - University of Chile
Hi,
I’ve just noticed an interesting thing. When I open roassal examples and then I #fork
some block, it’s not being executed. But as soon as I close examples it executes. Maybe
some #yield is missing somewhere?
Uko
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev