On Sat, Jul 26, 2014 at 8:23 AM, David T. Lewis <lewis@mail.msen.com> wrote:
On Sat, Jul 26, 2014 at 02:58:47PM +0200, Tobias Pape wrote:
>
> On 26.07.2014, at 02:59, Chris Muller <asqueaker@gmail.com> wrote:
> >
> > On Fri, Jul 25, 2014 at 11:21 AM, Eliot Miranda <eliot.miranda@gmail.com> wrote:
> > Hi All,
> >
> >     I depend heavily on fileOutAll in method list browsers.  For example, I'm trying to create versions of the VM's boolean cheat code for the Sista bytecode set and do this by filing out the code for the Newspeak set and editing it.  I tried to do this using "self systemNavigation browseAllSelect: [:m| ('*ooleanCheat*V*' match: m selector) or: [m sendsSelector: #booleanCheatV4:]]" to get a method list browser.  Then I was expecting to be able to use file out with nothing in the list selected.  This files out all methods in the list but...
> >
> > Deselection is broken!  I can't deselect the first item and hence can only file out a single definition .  Will whoever changed this please restore it asap? (in trunk)
> >
> >
> > Hi again, hey, I just realized!  There is a way to deselect in the MessageTrace.  It's called "Invert Level Selection" and its on the "more" menu (Shift+yellow click).
> >
> > Hot key for it is Command+Shift+I (capital "eye").
> >
>
> Wasn't that ?DoIt and invoke the inspector? ?

No, that's only from a code pane.  We're talking about from the upper pane of a MessageTrace or MessageSet.

But now I see I misspoke -- because I had been experimenting with Eliots question from a MessageTrace with only one message it it.

This is something I've wnated fixed for a long time, I'll see if I can spend a little time wiht it today and solve it.

BTW, why is it intuitive at all that NO SELECTION means ALL SELECTION for filing out?  Talk about unintuitive -- THAT sounds like it would be a bug in itself but, whatever..
 
To focus on Eliot's original question: The deselection mechanism works
in Squeak4.5-13352.image. It does not work in trunk now.

No, nothing has changed other than the traceMessages preference being set, which is way more important than occasionally filing out methods of a list.

Deselecting with the Control key is broken in 4.5 and for a long time before that.  As I said, we should focus on letting that "isControlled" input var to MessageTrace>>#toggleSelectionAt:shifted:controlled: be able to come in as a "true" and then everything should just work...

I'll see if there's an easy fix.