Re: [Pharo-dev] Message browser strange new behavior

Le 5/9/16 à 11:48, Denis Kudriashov a écrit : 2016-09-05 11:42 GMT+02:00 Nicolas Passerini >: I agree, it is sometimes difficult to find a class in the message browser because of the inheritance organization. I think that most often I do not want that

Re: [Pharo-dev] Message browser strange new behavior

2016-09-05 11:42 GMT+02:00 Nicolas Passerini : > I agree, it is sometimes difficult to find a class in the message browser > because of the inheritance organization. > I think that most often I do not want that, but also it might be useful in > other circunstances, so maybe the best would be to ha

Re: [Pharo-dev] Message browser strange new behavior

I agree, it is sometimes difficult to find a class in the message browser because of the inheritance organization. I think that most often I do not want that, but also it might be useful in other circunstances, so maybe the best would be to have both possibilities and make is easy to change from on

Re: [Pharo-dev] Message browser strange new behavior

Hi denis I looked at senders of iconNamed: and when I see a Smalltalk ui icons iconNamed: I change it into self iconNamed: when I can. May be I was also changing the superclass to be Model and this would be the problem. It would be nice to have the possibility to get the list displayed not

Re: [Pharo-dev] Message browser strange new behavior

I can't reproduce (or I not see it) Could you explain more? 2016-09-03 22:11 GMT+02:00 stepharo : > Hi > > > Often I look at senders and I modify them directly in the message browser > and I do not one by one. > > Now when I recompile a method I get a new one and I lose the next one. > > Am I the

[Pharo-dev] Message browser strange new behavior

Hi Often I look at senders and I modify them directly in the message browser and I do not one by one. Now when I recompile a method I get a new one and I lose the next one. Am I the only one to have this behavior. It is highly disrputing. Stef