Thanks again, that fixed it :) 2011/3/22 Esteban Lorenzano <[email protected]>
> yes... that's because NewInspector has it's own tool set. > I worked around by making NewInspectorToolSet inherits from DEVToolSet. > > best, > Esteban > > El 22/03/2011, a las 12:59p.m., AxiNat escribió: > > Is it possible that installing the NewInspector has broken the > autocompleter and some other stuff? > > 2011/3/22 AxiNat <[email protected]> > >> Thanks a lot, I do value them :) >> >> >> 2011/3/22 Henrik Johansen <[email protected]> >> >>> >>> On Mar 22, 2011, at 3:45 28PM, AxiNat wrote: >>> >>> > Hi list, >>> > >>> > First of all, I'd like to apologise just in case this is already a >>> known issue; I checked and couldn't find it around. >>> > >>> > I've started working with 1.2 RC a couple days ago, and I noticed the >>> inspector went back to (IIRC) several releases ago. In 1.1 we had tree >>> navigation and were able to run code in context, now you must open a new >>> inspector for each node and the code is always executed from the scope of >>> the root object. I've also noticed you can't remove items from a collection >>> straight from the UI anymore. >>> > >>> > Thanks! >>> > >>> > Bernat Romagosa. >>> >>> >>> The reason it's not included by standard any more I believe has mostly to >>> do with its performance when handling large collections. >>> If you value its features over its faults like some other here, it is >>> still loadable as an external tool, see: >>> ConfigurationOfNewInspector in the MetacelloRepository. >>> >>> Cheers, >>> Henry >>> >>> >>> >>> >> > >
