On Jan 13, 2015, at 4:26 AM, stepharo <[email protected]> wrote: >> >>> >>> I was doing a lecture and this is really sad to get all features gone. >> >> I think this is not so fair :). > > indeed but reopening an inspector is a pain.
Refresh buttons are useful for this and testing the inspector itself no? > >> >>> So I had to reinspect again. >> >> Yes. As Andrei said, it is a bug that will be fixed. >> >>> In addition GTInspector bubble is a pain because sometimes you really want >>> to keep the result and not inpect it. >>> Did you see my request to get that enter put the bubble contents into the >>> text pane? >> >> Did you see the reply? :) > > No where it is? >> >>> I'm sorry but I cannot use GT as it is now. >> >> That's a pity. > > but this is a reality. >> >> >>> And I'm working on the new version of Pharo by example and it would be good >>> to >>> have something full working. >> >> Besides these two problems, do you have others? > > I got confused with the inspector of arrays because we have to click on an > extra pane to see them if I recall. > It was so painfull with all the other problems that I stop to use GT to avoid > a huge frustration and get my job done. >> >> >> Cheers, >> Doru >> >> >> >>> Stef >>> >>>> >>>> Cheers, >>>> Andrei >>>> >>>> On Mon, Jan 12, 2015 at 12:14 PM, stepharo <[email protected]> >>>> wrote: >>>>> Hi >>>>> >>>>> GTInspector does not change the printString representation when we change >>>>> the printOn:. >>>>> Am I the only one to see this behavior? >>>>> >>>>> Stef >> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >
