Hi Marcel, I know what you are saying now, keep the same behaviors
with boolean options (or whatever) all in one class instead of
subclassing.  For a moment I thought you meant to simply delete
AlternatePluggableListMOrphOfMany (sheesh, what a name).  Sorry for
the poor humor.

Incidentally, the reason it is that kind of subclasssing mess is, back
in 2002, Squeak was being developed at a big company and one never
knew what the next version of Squeak would bring, so it was an
inhibiting factor for making very many base changes.  By making my own
subclass, I could keep my code separate.  Eventually it was integrated
into the base image, but left as-is because it had been simply working
for so long.

I'm trying to remember if there are any other differences in
requirements between the two other than the swipe gesture getting all
the elements -- maybe that would be a good behavior for where we use
the standard PluggableListMorphOfMany..?  (And fix the deselection, of
course).

On Thu, Sep 3, 2015 at 12:59 AM, marcel.taeumel <Marcel.Taeumel at hpi.de> wrote:
> Hi Eliot,
>
> just disable the preference "traceMessages". It makes MessageSet be replaced
> by MessageTrace, which uses a multi-selection list morph. That does not
> provide de-selection behavior.
>
> But we seriously *must* fix that mess with having subclasses for different
> selection behavior in list morphs. There should only be one
> PluggableListMorph that supports the common selection modes.
>
> You know, it's on my list. :P
>
> Best,
> Marcel
>
> P.S.: Arf woof LeChuck!! GRRRRRRRRR!! Woof woof woof ruff ruff... Wor-roof
> wuf Governor Marley. A-OOOOOOOOOOOOO!!!!! Ruff ruff ruff bow-roo wuf rowwf
> arroof LeChuck, GRRRRRR!!!!! Arf oof-oof Monkey Island™! *sniff sniff*
>
>
>
> --
> View this message in context: http://forum.world.st/Grrrr-how-come-I-can-t-deselect-in-a-list-browser-tp4847776p4847814.html
> Sent from the Squeak - Dev mailing list archive at Nabble.com.
>