Hi, I also just downloaded the latest Pharo 3.0 (30719), and I took the first class AIRootContext from the 'AST-Interpreter-Core' and dragged it to 'AST-Core' and the category is not changed. So, the problem comes from Pharo. See the picture attached. Cheers, Doru [image: Inline image 1] -- www.tudorgirba.com "Every thing has its own flow" On Fri, Jan 24, 2014 at 2:52 PM, Stephan Eggermont <stephan(a)stack.nl> wrote: -- www.tudorgirba.com "Every thing has its own flow"

I am on the run and I do not have time to do it properly via the bug tracker right now, so I am just dumping here what I found after looking into this briefly. In AbstractNautilusUI we have: AbstractNautilusUI>>dropInAPackage: aCollection into: receiver aCollection do:[:aClass | self showGroups ifTrue: [ * receiver addClasses: { aClass }.* * ???I do not quite know when this one happens???.* ActiveHand shiftPressed ifFalse: [ self selectedGroup removeClass: aClass. self updateClassView ]] ifFalse: [ * receiver addClass: aClass theNonMetaClass. * * aClass theNonMetaClass category: receiver name asString.* ActiveHand shiftPressed ifTrue: [ self selectedClass: nil. self updateClassView ] ifFalse:[ self selectedPackage: receiver. self selectedClass: aClass. self updateBothView ]]] The problem seems to be that the red lines work directly with the RPackage, but at the moment the right thing to do is still to go via setting categories and to let the SystemAnnouncer trigger the behavior in RPackage. Cheers, Doru On Fri, Jan 24, 2014 at 2:59 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: -- www.tudorgirba.com "Every thing has its own flow"