On Sat, Nov 21, 2015 at 10:36 AM, Ben Coman <btc@openinworld.com> wrote:
On Sat, Nov 21, 2015 at 4:31 AM, Nicolai Hess <nicolaihess@gmail.com> wrote:
Now there is a bug tracker entry for pharo 4.0 too, and a fix, ready for testing. 17057 BackPort Pharo4: 13854 frameSize calculated wrongly for #lineSegmentsDo:
Minor thought: The earlier comment on the original issue considered this a significant change that carried risk to implement prior to Pharo 4 release, and I think the same should be considered for backports. Perhaps see how the dust settles for a bit on Pharo 5, before integrating into Pharo 4. @Mariano, can you hang on and for a while load the slice manually or through a startup loader?
Sure, in fact it's already part of my image setup building :) So.... no need from me to be integrated since I can get the slice. And agree..maybe some testing in 5.0 may tell us how safe is to backport to 4.0. The good news is that it seems that also Marcus took a look too. Best, -- Mariano http://marianopeck.wordpress.com