we could add that to trait is this helps.

On Aug 3, 2010, at 7:25 PM, Mariano Martinez Peck wrote:

> You spotted a Metacallo bug. Thanks for the report. 
> 
> The problem is (I think) that in
> 
> OBCmdMetacello >> isActive
>     ^ ((target isKindOf: OBClassNode)
>         and: [ requestor isSelected: target ])
>             and: [ self selectedClass isMetacelloConfig ]
> 
> 
> selectClass can be a Trait, not necessary Behavior.
> 
> If you see, Metacello implemented 
> 
> Class >>isMetacelloConfig
> 
>     ^false
> 
> But nothing in Trait.  So...you can just add it also in Traits or...
> 
> Maybe moving that method to Behavior helps? I am not sure how Traits is 
> implemented. Can you check?
> 
> The problem is that Gemstone doesn't have Traits...thus problably why the bug 
> exists :)
> 
> Cheers
> 
> Mariano
> 
> 
> 
> On Tue, Aug 3, 2010 at 6:16 PM, Jochen Riekhof <[email protected]> wrote:
> Hi...
> 
> just noticed that I get a walkback after creating a Trait and then opening 
> the Context-Menu on the browser's  classes list pane. It complains
> MessageNotUnderstood: Trait>>isMetacelloConfig
> 
> Adding the missing method to Trait solves the issue. Probably it is just 
> missing from {ob-metacello} package?
> 
> Ciao
> 
> ...Jochen
> 
> 
> _______________________________________________
> Pharo-project mailing list
> [email protected]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
> 
> _______________________________________________
> Pharo-project mailing list
> [email protected]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Reply via email to