Another related issue: 12535 <https://pharo.fogbugz.com/f/cases/12535/To-many-updates-on-the-methods-list> To many updates on the methods list (changes aren't applicable anymore, because to many things had changed).
Sometimes I am working on this and try to solve this. But I failed so far. The way Nautilus holds the current selection (model and UI) and how it propagate changes (selectX, selectXwithoutChangingSelection, select silenty ...) doesn't really work good ( or I just don't understand it). (And with rubric as TextModel, this is getting even more complicated). 2015-09-04 9:34 GMT+02:00 Christophe Demarey <[email protected]>: > > Le 4 sept. 2015 à 09:22, Yuriy Tymchuk a écrit : > > > Hi, > > > > I find announcements in Nautilus a bit strange. I guess you are familiar > with QualityAssistant. To display the critics about the currently selected > entity I need to know which one is selected. There is > NautilusMethodSelected and NautilusClassSelected announcements. But here is > a small detail, if you select a method, both of them are fired i.e. for the > method’s class and the method itself. > > > Does anybody need this double announcing? (Maybe it is quadruple, I > haven’t checked for a package and protocol) > > > And the best is that the UI is refreshed for each announcement. Then you > understand why Nautilus is slow. > Franck did some improvements but Nautilus still refresh itself far too > much (there was 12 refresh calls for the source code panel ...). > > It looks like a design flaw: there should be only one announcement for a > selection change. You could define PackageSelectionChanged, > ClassSelectionChanged, ProtocolSelectionChanged, MethodSelectionChanged, > each one with more or less info (I mean method will have the protocol, > class, and package).
