Dnia 02.04.2015 16:07:54, Tobias Pape napisał(a):
> Hi Mateusz
> 
> On 02.04.2015, at 16:06, Mateusz Grotek <unoduetre at poczta.onet.pl>  
> wrote:
> 
> > Dnia 02.04.2015 15:19:10, Tobias Pape napisał(a):
> >> Hey
> >> On 02.04.2015, at 15:20, Mateusz Grotek <unoduetre at poczta.onet.pl>  
> wrote:
> >> > Is this problem already solved in the forthcoming 2.6 or it's  
> new?
> >> >
> >> > To reproduce:
> >> > 1. Create a class.
> >> > 2. Rightclick on the class name and choose "Rename class".
> >> > 3. Enter the new name and accept.
> >> This is fixed for 4.5 and Trunk (upcoming 4.6).
> >> For 4.5 please use the update functionality.
> >> Best
> >> 	-Tobias
> > Hi,
> > (Of course I wanted to say 4.6, not 2.6) Well, it seems the update  
> (click on logo, and then "Update Squeak") does not solve the problem.  
> Can you verify it?
> > Mateusz
> 
> 
> Can you explain what happens after step 3 and what should happen?
> It might be we are talking about different bugs.
> 
> Best
> 	-Tobias
> 
Sure. After accepting the new name an exception shows up.
Its message is: MessageNotUnderstood: PutTheRenamedClassNameHere  
class>>updateMethodBindingsTo:
The exception is called from the following line:
   aClass updateMethodBindingsTo: newBinding.
of: Environment>>renameClass:from:to:

After closing the exception window it reopens ad infinitum. It's  
impossible to work in the image after that, because more and more  
exceptions show up after doing some trivial things.

It's probably related to the new environments functionality.

Best wishes,
Mateusz