Re: [Pharo-dev] problems with RPackage and cie...
Esteban wrote:
I would really like a reproducible case⦠in the form of an image, if no else.
btw⦠moose 5.0 images are severely broken in that area, so if you are using one of them you *will* have problems.
I can deny that it is a Moose problem, I can reproduce it in Pharo 30716 on mac Open the image, open a Nautilus browser Add new package AZ Select AST-Core, Nodes Select RBProgramNode Copy the class with right-click menu Rename to AZProgramNode Enter your name (should have happened when creating the new package!) Drag AZProgramNode to AZ Category is not updated. Stephan
Hi stefan This is good that you could reproduce it because I was mad at it. I found another case in Moose but esteban could not reproduce it in plain Pharo. We just spent some times chasing the wrong bug :) Stef On 24 Jan 2014, at 14:51, Stephan Eggermont <stephan@stack.nl> wrote:
Esteban wrote:
I would really like a reproducible case⦠in the form of an image, if no else.
btw⦠moose 5.0 images are severely broken in that area, so if you are using one of them you *will* have problems.
I can deny that it is a Moose problem, I can reproduce it in Pharo 30716 on mac
Open the image, open a Nautilus browser Add new package AZ Select AST-Core, Nodes Select RBProgramNode Copy the class with right-click menu Rename to AZProgramNode Enter your name (should have happened when creating the new package!) Drag AZProgramNode to AZ Category is not updated.
Stephan
participants (2)
-
Pharo4Stef -
Stephan Eggermont