On Thu, Dec 31, 2009 at 10:14 AM, Lukas Renggli <renggli@gmail.com> wrote:
I've encountered and fixed that bug a long time ago in OB-Morphic in
OBLazyListMorph>>display:atRow:on:. This is the same bug in
O2-Morphic. Compare with "[Pharo-project] We need to do something,
seriously!!!! [WAS] Fwd: Issue 1721: Refactoring appears to be broken
in web dev image. e.g. OBClassNode(Object)>>doesNotUnderstand:
#dynamicProtocols".




Lukas, there is something I really don't understand. Are you sure that in this thread you are answering to the bug 1724 ?

http://code.google.com/p/pharo/issues/detail?id=1724

Because I realised that this get fixed if you load the fix to the bug 1433

http://code.google.com/p/pharo/issues/detail?id=1433

And this seems to be quite different to what said

Even more, 1721, the bug you told me, happens using OB

Lukas

2009/12/31 Mariano Martinez Peck <marianopeck@gmail.com>:
> Issue: http://code.google.com/p/pharo/issues/detail?id=1724
>
> Pharo image: pharo1.0-10502-rc1web09.12.2
> Pharo core version: 10502
> Virtual machine used: Squeak 4.2.2beta1U.app
> Class browser used if applicable: O2PackageBrowserAdaptor.
>
> Steps to reproduce:
> 1. Open a class browser
> 2. Click on the class ByteArray from the package Collection-Arrayed
>
> 'MessageNotUnderstood: ByteSymbol>>hasWideCharacterFrom:to:'
>
> I attach PharoDebug.log
>
>
>
>
>
> _______________________________________________
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>



--
Lukas Renggli
http://www.lukas-renggli.ch

_______________________________________________