Thanks nicolas! I love to read this mail :) Stef
On Sep 16, 2013, at 4:18 PM, Nicolas Passerini <[email protected]> wrote: > Last Saturday in the Pharo Sprint in Buenos Aires, together with Mariano Peck > and Guido Chari we have been trying to address issue 11605, i.e. using > NewList in Nautilus. I am still trying to finish with this task, and I have a > few questions, may be somebody here can enlighten me. > > We have encountered some problems with multiple selections. First, the list > has 4 ValueModels for its selected elements: selectedIndex, selectedIndexes, > selectedItem, selectedItems. I would like to understand more clearly how > should we use them. In particular I find difficult to bring the plural > versions and the singular versions together. > If I select more than one element in the list, it seems that the value in the > selectedItem/selectedIndex points to the last one I clicked. But then the > model in Nautilus is receiving two updates, one from selectedItem/Index and > the other from selectedItems/indexes, should we just ignore the singular one > or what? > > Second, in my linux the list doesn't seem to receive ctrl+click events. Any > clue about this? > > > Finally, another question not related to multiple selections. > The old list (it was a PluggableIconListMorph) has a "searchedElement" > attribute. Looking at the categories list in Nautilus, the usage is so: if > you have not selected any category (i.e. you are seeing the method of all > categories in a class) and you click on a method in the method list, the > searched element of the category list points to the category of the selected > method. This is different from selecting the category, because selecting the > category would filter the method list. It also highlights the category in a > different color. > > So, my question is, should we keep this behaviour while migrating Nautilus to > new lists o not? > If the answer is yes, I would ask how to do it, because the NewList does not > seem to have this feature. Should I add the searchedElement to the NewList or > is there another way to achieve the same behavior? > > > > >
