>
> I'd like to make a UI suggestion that would ameliorate quite a few cases
>> of this need - use a PluggableTreeMorph (as we do in the
>> Explorer-inspector) to show the tree of messages.
>
>
I remember now.  In Pharo's, there was no need to select "implementors" at
all, you simply keep expanding the tree of sent messages.  I don't think it
could backtrace at all, though.


> It would allow a bit more control over what you see at any point, without
>> removing messages  with the cmd-D etc as now.
>>
>
It'd be less control, not more, because you can't trim individual levels
with Cmd+d.  You'll always have either all 67 #at:'s (expanded) including
the ones totally unrelated to what you want, OR none of them (collapsed).
Try out Pharo's, you'll probably hate it.  So you can't get rid of Cmd+d,
and nor would it be good to combine it with expand / collapse capability,
because those functions would be confusingly ambiguous to the goal of
tracing code.

 - Chris

>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20220228/815d02ba/attachment-0001.html>