Issue 1721: Refactoring appears to be broken in web dev image. e.g. OBClassNode(Object)>>doesNotUnderstand: #dynamicProtocols

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Issue 1721: Refactoring appears to be broken in web dev image. e.g. OBClassNode(Object)>>doesNotUnderstand: #dynamicProtocols

Stan Shepherd
NB this logs a particular walkback, but the whole area appears to be
unworkable in the web dev image. Please could the maintainers click, right
click, middle click on each part of refactoring browser, take each menu
item, etc. This will be much quicker than logging one bug at a time.
If this turns out to be the last one, my apologies in advance.
Thanks.   ...Stan


VM: unix - i686 - linux-gnu - Pharo0.1 of 16 May 2008 [latest update:
#10074]
Image: PharoCore1.0rc1 [Latest update: #10502] pharo1.0-10502-rc1web09.12.2

Class browser used (if applicable):  OR2PackageBrowser.

OBClassNode(Object)>>doesNotUnderstand: #dynamicProtocols
        Receiver: OBClassNode<ShortIntegerArray>
        Arguments and temporary variables:
                aMessage: dynamicProtocols
                exception: MessageNotUnderstood: OBClassNode>>dynamicProtocols
                resumeValue: nil
        Receiver's instance variables:
                metaNode: Class
#allCategory->AllMethodCategory
#categories->MethodCategory
#dy...etc...
                navigation: an O2DefaultEdgeNavigation
                theClass: ShortIntegerArray

O2MetaEdge>>nodesForParent:
        Receiver: #dynamicProtocols->DynamicProtocols
        Arguments and temporary variables:
                aNode: OBClassNode<ShortIntegerArray>
        Receiver's instance variables:
                label: 'dynamicProtocols'
                selector: #dynamicProtocols
                metaNode: DynamicProtocols
#methods->Method

                navigation: an O2DefaultEdgeNavigation
                isDropEdge: nil

...