Is it possible that installing the NewInspector has broken the autocompleter and some other stuff?<br><br><div class="gmail_quote">2011/3/22 AxiNat <span dir="ltr">&lt;<a href="mailto:tibabenfortlapalanca@gmail.com">tibabenfortlapalanca@gmail.com</a>&gt;</span><br>

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Thanks a lot, I do value them :)<div><div></div><div class="h5"><br><br><div class="gmail_quote">2011/3/22 Henrik Johansen <span dir="ltr">&lt;<a href="mailto:henrik.s.johansen@veloxit.no" target="_blank">henrik.s.johansen@veloxit.no</a>&gt;</span><br>

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div></div><div><br>
On Mar 22, 2011, at 3:45 28PM, AxiNat wrote:<br>
<br>
&gt; Hi list,<br>
&gt;<br>
&gt; First of all, I&#39;d like to apologise just in case this is already a known issue; I checked and couldn&#39;t find it around.<br>
&gt;<br>
&gt; I&#39;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&#39;ve also noticed you can&#39;t remove items from a collection straight from the UI anymore.<br>



&gt;<br>
&gt; Thanks!<br>
&gt;<br>
&gt; Bernat Romagosa.<br>
<br>
<br>
</div></div>The reason it&#39;s not included by standard any more I believe has mostly to do with its performance when handling large collections.<br>
If you value its features over its faults like some other here, it is still loadable as an external tool, see:<br>
ConfigurationOfNewInspector in the MetacelloRepository.<br>
<br>
Cheers,<br>
Henry<br>
<br>
<br>
<br>
</blockquote></div><br>
</div></div></blockquote></div><br>